Zenith’s errors say what happened and what to do next. These are the common ones.
“Google blocks sign-in inside apps”
Google refuses to sign in inside embedded browsers. Sign in with your Zoho password and one-time code, or choose Continue with Chrome to use the session from your browser through the paired extension.
“Creator: sign-in needed”
Your Zoho session expired. Syncs and ships pause and a Reconnect banner appears; sign in again in the Creator tab and they resume.
Push failed
The failed step shows a plain-language summary first and Creator’s own error second, mapped to the line in your draft. Choose:
- Ask Zenith to fix: the agent proposes a fix inside the step. Because the code changed, the run needs a fresh plan and preflight.
- Retry, Skip, or Roll back run.
If someone changed the function in Creator after Zenith took its snapshot, the step offers View 3-way instead: Zenith never overwrites a later change. Nothing after a failed step runs until you choose.
Drift detected
Someone changed a component in Creator after Zenith’s last pull. The Changes tab shows a banner on that component: Take live discards your draft, Keep my draft rebases it on the live code (your push will replace their change), and Compare draft with live now shows the two side by side. Preflight blocks a ship while drift is unresolved.
Rollback conflict
Rollback restores a snapshot only if the live function still matches what Zenith pushed. If someone changed it since, the step shows a conflict with a three-way view instead of overwriting their work.
License can’t be checked
The license is a signed lease that works offline for a grace period. If Zenith can’t reach the license server, it keeps working and shows the grace state; it never downgrades you because of a server error.
Report a problem
Help → Report a Problem… opens Settings → Privacy; choose Create bundle. Zenith writes a diagnostics bundle on your Mac with secrets removed. Nothing is uploaded: attach it to an email to support@zenithsuite.io if you want us to look.