# Troubleshooting

## I did not receive an email code

Check spam folders and your email address. Deployment owners should verify the Supabase email OTP template and SMTP configuration. Google login is an alternative when enabled.

## The task is waiting

Only one generation runs per account. Jobs also wait for available worker capacity. Refreshing or closing the page does not cancel a queued or running task.

## AI is unavailable

The model service may not be configured, a task may have reached its token budget, or the provider API may be unavailable. Unlimited conversations and deployments retain safety checks, concurrency limits, and per-task token protection. No successful artifact is shown unless generation and independent validation complete.

## My token is rejected

Use the `app...` Serverless CLI token, not the normal numeric Bot API token. Ensure Serverless is enabled in BotFather. Replacing a token is supported for the same Telegram app.

## Type checking or local simulation failed

Read the file, line, and column in the validation report. Two automatic repairs are included. After they fail, simplify the requirement or explain the error in chat and create a new generation. The old live bot stays unchanged.

## Publishing needs attention

Read the deployment details. Common causes are external cloud edits, incompatible schema changes, expired credentials, webhook drift, and network uncertainty. Correct the underlying problem and retry; cloud state is reconciled before another publish.

The free plan includes Telegram and email guidance 12 hours a day, 7 days a week.

Never share access tokens or model credentials in support messages. Include the task ID and visible error instead.