Sometimes in Rezi, a brochure generates correctly but does not save to the system. This can prevent agents from accessing or sending the brochure later. This article explains the most common causes and user-side checks.
Session Timeout – The user was logged in too long without activity before saving.
Browser Cache/Connection – Cached data or a weak internet connection interrupted the save.
File Size Limitations – Large images or content causing timeouts at the save step.
System Glitch – A temporary Rezi process failure.
Ensure you are still logged in (session not expired).
Attempt to save the brochure again immediately.
Clear browser cache and cookies.
Retry saving the brochure in Chrome or Edge.
Check internet connection stability.
Retry saving with fewer open browser tabs to reduce memory use.
If the brochure still doesn’t save, regenerate it and try saving again.
Level 1 (Support Agent) → Session check, retry save, cache clear, connection check.
Level 2 (Branding Support) → If template-related issue suspected (rare).
Level 3 (Development) → If saving failures affect multiple users/system-wide.
[Clearing Cache in Chrome/Edge] (internal link)
[Session Timeout in Rezi] (internal link)
Trigger phrases:
“Brochure not saving”
“I created a brochure but it didn’t save”
“Saved brochure missing”
Response flow for AI:
Ask if the user’s session timed out before saving.
Suggest clearing cache and retrying in Chrome/Edge.
Check if the user’s connection was stable.
Suggest regenerating and saving again.
Escalate if persistent or widespread.
Tone for AI:
Empathetic (“That’s frustrating — let’s make sure your work isn’t lost again”).
Clear reassurance that retrying + cache checks usually fix the issue.
Direct hand-off if persistent.