Recover when angle generation does not finish
Check saved work, evidence and credits before retrying a generation run.
A slow run, a rejected request and a completed run whose results are hidden need different responses. Start with what the app actually shows.
While a run is processing
The product-page button changes to Writing angles. A batch can appear together when it finishes, so an empty result area during processing is not necessarily a failure.
Avoid clicking generation again to make it faster. Reopen the product to check the current state, and look for the completed angles before submitting a new batch.
Follow the error
| What you see | What to check |
|---|---|
| Insufficient credits | Correct workspace, current balance and the action you requested. |
| Source cannot be read | A public product-page URL that opens without signing in. |
| Too little usable evidence | Accurate product details and relevant source material. |
| Request or service error | Whether a result was saved before the error appeared. |
| Results missing after completion | Workspace, Product focus, Ideas/Winners and Show all. |
Retry deliberately
Correct the cause when possible, then submit one new request. A new batch is a new metered action. An automatic retry of an existing run is not the same as deliberately starting another run.
Angle generation uses credits for the angles actually created. If a charge seems wrong, include the time of the request and your balance in a support message. The team can check that specific run.
When to contact support
Send the workspace, product, time, exact error and whether any angles appeared. Include a screenshot of the result or error state. Never include passwords or payment-card details.
Use report a problem for a concise checklist.