Troubleshooting
Document build stopped or failed
In short
If a Slaide build stops, read the message in the chat and inspect the pages already saved. Reopen the document to check whether work is still running before retrying. Resolve a credit or page limit first; use Try again when it is offered. A browser disconnection alone does not cancel a server-side build.
What happened to the build?
The retry banner says the request did not finish; it does not identify every cause. Read the message in the conversation for the actual reason. A stopped request, empty credits, a page limit and a lost browser connection need different next steps.
What if the browser disconnected or stopped updating?
Step 1: Reopen the same document
Return through your library instead of creating another document. A lost connection alone does not cancel server-side work.
Step 2: Inspect status and pages
Check whether new pages appeared and whether the request is still running. Do not send the same request again while the original is working.
Step 3: Use Stop only to cancel
Choose Stop when you intend to stop the request. If Slaide reports that stopping could not be delivered, check the status again instead of assuming cancellation succeeded.
There is no fixed completion time for every document. Research, images and complex pages can take longer. A quiet interval alone does not prove a failure; use the current status and explicit error message to decide what to do.
What if credits or page limits stopped progress?
The free document builds the first 3 pages of its plan. Remaining planned pages are not the same as a failed build. Use the available Finish building flow if you want to complete them under the applicable paid access.
For empty credits, read Not enough credits and inspect your balance and plan. For a page-limit message, reduce the requested scope or choose access that covers it. Repeating an unchanged request cannot raise those limits.
A stopped request may have done useful work. Inspect the existing document before asking for missing pages. Do not assume a retry is free or that every incomplete run has zero usage; Credits explained describes how usage is charged.
How do I retry without losing context?
Step 1: Read the error and inspect progress
Check the last message, the completed pages and any still-running status. Keep your source files and original request available.
Step 2: Use the offered retry
If Try again is shown, use that action after resolving the reported cause. A deliberate Stop restores the request to the composer so you can review it before sending.
Step 3: Ask for the remaining work
If pages are already usable, name what remains instead of asking to rebuild everything. Check the result before exporting.
Pages 1 to 3 are finished. Continue with the remaining planned pages, using the same source files and design. Keep the existing pages unchanged unless a correction is necessary.
If the same error returns, contact support with the document link, exact message, approximate time and what you tried. Remove sensitive details from any screenshot. Do not send your password or payment details.
Frequently asked questions
Does closing the tab cancel generation?
A browser disconnection alone does not cancel a server-side build. Reopen the same document and check its status. Use Stop when you intend to cancel the request.
Why did only three free pages appear?
The free document builds its first 3 planned pages. The remaining plan can stay visible without being built. Check the Finish building flow and the applicable access requirements.
Is retrying always free?
Do not assume that. Work already performed can affect usage, and a retry can perform additional work. Inspect the reported cause and your credit balance before starting it.