Troubleshooting

The most common issues and how to fix them. If you’re still stuck, reach out to support.

Content isn’t generating

  • Check that your Apify API key is valid and hasn’t run out of credits.
  • Confirm the Stage 1 scraper is active/scheduled.
  • Verify the Instagram profiles you’re scraping are public — private accounts can’t be read.
  • Make sure you have at least one active character.

Pipeline stopped generating — API credits exhausted

If the pipeline was running fine and suddenly went quiet, the most likely cause is that one of your third-party services ran out of credit. Each stage depends on a paid API, so an empty balance halts everything downstream.

  • Open the API Status dashboard and look for any 🟡 Low or 🔴 Critical card — most often FAL.ai (video) or Apify (scraping).
  • Top up the affected service using its “Top up” link, then hit Refresh to confirm the balance recovered.
  • Re-trigger the pipeline (or wait for the next scheduled run) to resume generation.
  • See API Credits for recommended minimum balances and how to set up low-balance alerts.

Videos aren’t posting

  • Check that your platform OAuth tokens haven’t expired — reconnect if needed.
  • For X (Twitter), confirm you’re on the paid Basic tier (video upload requires it) and have API credits.
  • Verify each platform app has the required posting permissions/scopes approved.
  • If a review gate is enabled, remember posts wait in your queue until you approve them — see The Pipeline.

Daily limit reached

  • Each plan has daily caps on assets processed and posts published.
  • Limits reset at UTC midnight.
  • Need more headroom? Upgrade your plan.

Payment issues

  • Update your payment method from the billing section of your dashboard.
  • If a payment fails, your account keeps limited access while we retry; generation and posting may pause until payment succeeds.
  • Once payment goes through, the pipeline reactivates automatically.

Contact support

Still stuck? Email hello@dripcode.xyz and include your account email and what you were doing when the issue happened.