Overview
An enabled bundle is not guaranteed to be selected. It must also be ready, unconsumed, relevant, outside cooldown, and reached only after every usable Script state is complete.
- Find whether Scripts still block Gallery.
- Resolve bundle-specific readiness or reuse issues.
- Test matching with a normal relevant fan message.
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 confirm no active Script, Waiting Payment, post-media sequence, or rotation remains.
- Open the bundle and confirm Enabled is on and readiness shows no blocked media or pricing issue.
- Check whether the bundle or its Paid media was already sent or purchased in that conversation.
- Review the bundle media context and compare it with the latest fan message and known preferences.
- Send a new normal fan message after the Scripts-first handoff and observe the eligible selection again.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Enabled is not enough | Readiness, relevance, prior use, cooldown, and current conversation state still apply. |
| Scripts-first block | Gallery cannot run while any usable Script lifecycle or required interval remains. |
| Consumed Paid bundle | A successfully sent Paid bundle does not return to normal selection even without a purchase. |
| No forced match | Telestars can continue the relationship or stop rather than send unrelated eligible content. |
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 bundle is Active but never offered | Check fan-specific prior delivery, Script exhaustion, relevance, and cooldown rather than only the bundle list status. |
| Another bundle is selected | Compare media context, fan request, prior use, Content tier, and readiness across the eligible candidates. |
| No bundle is selected after exhaustion | Confirm at least one relevant, enabled, ready, unconsumed bundle remains. |
Best practice
Test Gallery with the exact fan history because eligibility and prior consumption are conversation-specific.