Overview
Script progression depends on the exact fan history and current state. A step can be waiting for its minimum, ready inside its range, hard due at its maximum, blocked by delivery, or paused behind Waiting Payment, follow-ups, rotation, or manual takeover.
- Identify the current Script and next step.
- Distinguish normal pacing from a real blocker.
- Prevent Gallery or another Script from hiding the issue.
Before you start
- Select the exact bot, creator profile, and fan conversation affected by the issue.
- Keep the full recent Telegram conversation available while diagnosing.
- Read the current status shown in Telestars before changing configuration.
Step by step
- Open the fan conversation and identify the active Script and last completed step.
- Open that Script and confirm the next step still exists, is ordered correctly, and uses ready media.
- Check whether AI General Mode or Sexting Mode controls the current reply range.
- Check for active Waiting Payment, post-media follow-ups, rotation, manual takeover, or Telegram permission issues.
- Continue with a normal fan turn and verify a hard-due step sends or exposes the real blocker.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Before minimum | The next step cannot send early, even after a direct content request. |
| Open range | Between minimum and maximum, Telestars may keep the conversation going or send the exact ready step. |
| At maximum | The step is due and must deliver unless a real permission, safety, freshness, or delivery issue blocks it. |
| State ownership | Waiting Payment, configured follow-ups, and rotation must complete before another product path can progress. |
Verify the result
- Repeat the exact affected path with a new real Telegram inbound message.
- Confirm the expected reply or delivery is visible in both Telegram and Fan Inbox.
- Verify the fix did not change Script order, price, media, language, or purchase state.
Troubleshooting
| If you see this | What to check |
|---|---|
| The counter appears to restart | Confirm whether this is the first-ever step or a later transition; later Scripts use Sexting Mode. |
| The step is hard due but only text is sent | Check media readiness and Telegram delivery, then keep the atomic step pending until it can send correctly. |
| Gallery content appeared instead | Confirm all Scripts were truly exhausted; Gallery must not interrupt the active Script path. |
Best practice
Diagnose from the current fan-specific Script state, not only from how the Script looks in the editor.