Troubleshooting Overview
How to approach issues in ReelBot
ReelBot is designed to be predictable, explicit, and safe.
When something doesn’t behave as expected, it’s usually because:
- a limit was reached
- a dependency changed
- an external service responded unexpectedly
- a step requires regeneration
This section helps you identify what’s happening and what to do next.
Before troubleshooting
Before assuming something is broken, check:
- Status messages shown in the UI
- Usage counters (AI credits, videos, posts, storage)
- Draft state (was something cleared intentionally?)
- Warnings you may have confirmed earlier
ReelBot always explains why an action is blocked.
How ReelBot surfaces issues
ReelBot does not fail silently.
Issues are surfaced through:
- inline error messages
- disabled actions with explanations
- warning dialogs
- status indicators on projects or posts
If something is blocked, the reason is visible.
Common issue categories
Most issues fall into one of these categories:
Creation issues
Examples:
- script or voice not generating
- video stuck in processing
- regeneration clearing steps
Usually related to:
- AI credit limits
- impacted step warnings
- content dependencies
Publishing issues
Examples:
- publish button disabled
- post fails to publish
- platform unavailable
Usually related to:
- missing or disconnected channels
- post quota limits
- platform-specific restrictions
Account & authentication issues
Examples:
- login confusion
- email not verified
- password reset problems
Usually related to:
- social login detection
- verification requirements
- authentication method mismatch
Subscription & limit issues
Examples:
- actions suddenly blocked
- uploads disabled
- publishing unavailable
Usually related to:
- plan limits
- daily or monthly resets
- storage usage
External platform issues
Examples:
- TikTok, X, Instagram, or YouTube publish failures
- authorization expiration
Usually related to:
- platform outages
- expired permissions
- temporary API issues
Drafts as a safety net
Many issues are non-destructive because ReelBot uses drafts.
Drafts ensure:
- work is not lost
- partial progress is preserved
- regeneration is safe
If something fails, your draft is usually intact.
What to do when something fails
When an action fails:
- Read the message shown — don’t skip it
- Check relevant limits or requirements
- Retry only after addressing the cause
- Avoid repeating the same action blindly
Retrying without fixing the cause won’t help.
When regeneration is required
Some changes require regeneration to preserve quality.
Examples:
- changing duration
- changing tone
- changing script after voice generation
This is intentional and documented — not an error.
When to contact support
Contact support if:
- the UI shows an error with no clear resolution
- a project is stuck indefinitely
- usage counters behave unexpectedly
- something contradicts the documentation
When contacting support, include:
- your User ID
- the feature you were using
- the exact error message
- what you expected to happen
This speeds up resolution significantly.
What troubleshooting is NOT
Troubleshooting is not:
- guessing
- retrying randomly
- deleting work prematurely
- assuming data loss
ReelBot prioritizes safety over speed.
The CreatorOps perspective
In CreatorOps, systems must fail loudly and recover cleanly.
ReelBot:
- exposes dependencies
- blocks unsafe actions
- preserves work via drafts
- explains limits clearly
Troubleshooting is part of operating a system — not a sign of failure.
Where to go next
If you’re facing a specific issue, continue to:
- Creation Issues
- Publishing Issues
- Account & Login Issues
- Subscription & Usage Issues
This overview is your map — the next pages are the tools.