Why an edition did not publish and how to continue
Start in Autopublish → Queue. Check the workspace and filters. Open the edition before taking another action. Preparation, approval and actual delivery are different events; the interface preserves those differences for author series and news rules.
| What you see | What to check |
|---|---|
| Paused, no next run | Review the configuration and matching preview, then enable if intended |
| Queued or generating | Wait for the existing job; do not start another paid trial to speed it up |
| Ready trial | A trial never sends itself; inspect it, enable future runs or explicitly publish ready versions |
| Ready scheduled author edition awaiting review | This series uses review mode; open the edition and send ready versions when satisfied |
| News candidate needs review | Approve or reject through the site's news dialog or the configured moderator flow |
| Partially ready | Inspect each language variant; successful variants and the shared image are retained |
| Scheduled or waiting to send | Check each placement time and timezone, not only the series time |
| Failed | Check balance, catalog availability, required images, language/section validation and account permissions |
| Outcome unknown | Inspect the destination channel first; the request may have succeeded before its receipt was saved |
Delivery retry is different from generation
Delivery details and retry shows the saved steps for a document delivery. A delivery retry reuses the saved text and images; it does not call a text or image model again. Delivery infrastructure can still have a cost. Confirmed chunks are retained. For an unknown outcome, first check the destination and explicitly acknowledge duplicate risk before retrying.
Older news deliveries may have a saved message ID without a document receipt. The UI does not invent missing receipts or offer an unsupported document retry.
Generate text again creates a new paid version. Resume generation can reuse retained source snapshots, ready variants and a known image output, but missing stages can still incur model/storage charges. These actions are not free substitutes for a delivery retry. Published variants cannot be regenerated through the author edition action.
After an interrupted trial request, inspect the existing queue first. The editor retains the logical trial intent while awaiting a confirmed response, so a repeated request can find the same edition rather than charging for a new one.
Common fixes
- Insufficient balance or daily limit: check Billing. A top-up or limit change is a separate manual decision; a retry does not bypass budgets.
- Catalog/image unavailable: open Materials, synchronize the API catalog or fix the owning source/manual item. Models never receive its access token. Generated images need the actual required references.
- Missing section or wrong language: inspect the failed version. Required sections must occur exactly once; fixed headings are not evidence that generated prose uses the correct language. Correct the series instruction for future runs; do not assume changing it rewrites an old frozen edition.
- Telegram permissions/session: reconnect the publishing account and verify its channel rights in Delivery channels. Enabling the schedule cannot repair a revoked Telegram session.
- Only one channel succeeded: check per-channel receipts. Do not regenerate all languages or repost a confirmed successful channel just because another failed.
The overview shows recent author editions and the news queue; use an individual series' edition list for older results. A bounded history is not a claim that no earlier editions exist.