Troubleshooting

Recover from common chat, Wapp, file, integration, automation, and extension problems.

Chat is waiting for input

Check the latest message for a clarification, tool approval, or plan review. In Manual approval mode, Cheqq pauses until you explicitly approve or deny the next tool call. Sending a new message while an approval is still pending automatically denies it — if the request is no longer correct, stop and send a narrower instruction instead of talking past the pending approval.

A tool is unavailable

Confirm that you are in Agent mode, the relevant integration is connected (not showing "Needs reconnect"), and you opened the Wapp or automation that owns the capability. Available tools depend on the current context.

A checkpoint is partial or unavailable

A partial checkpoint means the turn continued but Cheqq could not capture every supported local subject. Open its Restore confirmation to see what was captured and which state may be skipped. When the primary artifact capture is unavailable, Restore is disabled; conversation Fork can still be available.

Do not assume Restore reverses external effects. Sent messages, completed payments, published content, finished workflow runs, and other external actions remain in place. Review the non-reversible effects listed in the confirmation.

Restore, Fork, or Undo restore is unavailable

Wait for the active stream, tool approval, browser handoff, or queued-message transition to finish. Undo restore is shown only for the latest applicable restore and disappears after it is used or a new user turn moves the conversation forward.

If an artifact Fork needs a new name or would exceed a plan limit, resolve that requirement before it can be materialized.

Artifact Undo or Redo is unavailable

Undo needs a retained parent entry; Redo needs an active redo path. A new committed change after Undo clears that path, although the abandoned entry remains browsable until it expires.

History is collaborative. If someone or an agent saved a newer change, refresh the History drawer and review the new current entry before trying again. Cheqq rejects a stale history action rather than undoing an unexpected collaborator's work.

A restore completed with warnings

Review the affected and skipped subjects in the result. A workflow restored from Trash stays inactive if trigger registration cannot be reconciled safely. For Wapps, large comparisons may report that additional changes were truncated; that limits the displayed diff, not the retained version itself.

See History and recovery for the distinction between conversation recovery and artifact history.

Connecting an integration silently fails

If a provider's authorization popup is blocked, closed before finishing, or you deny access on its consent screen, Cheqq currently resets the Connect button back to idle without an on-screen error. If Connect doesn't visibly succeed, check that popups are allowed for Cheqq and try again — don't assume a silent failure means something is broken.

An integration needs reconnecting

A connection moves to Needs reconnect when its token expires or a provider revokes it. Open Integrations, select the affected service, and follow the reconnect action. Complete the provider authorization, then return to Cheqq and verify its status.

A file will not upload

Confirm the file is within your plan's per-file size limit (check Billing if unsure which applies). Retry from the Files page and wait for the current upload to finish before starting another.

An automation did not run

Open the automation and check that its configuration was saved — Run stays disabled with a tooltip while required fields are unresolved.

Confirm required integrations are connected.

For triggered workflows, confirm both the workflow and the specific trigger are active — pausing either one blocks future firings without cancelling anything already running.

For schedule triggers, check the cron expression and timezone; invalid values are rejected with an inline error rather than silently skipped.

For webhook triggers, confirm the incoming payload matches any schema you configured — a mismatch returns an error to the caller and never starts a run.

Use Run now or Dry run to separate workflow configuration errors from trigger-delivery problems.

Review the latest run's output for the failing step — a step with Power Mode enabled shows an amber warning badge and a "Last Run Error" card with a suggested fix.

If you're running many workflows at once, note that concurrent runs are capped per account — an unusually busy account may need to wait for one run to finish before another starts.

A Mailhook isn't firing

Confirm the address is active in Settings → Mailhooks, and that any Only from / Never from / Subject contains filters on the trigger actually match the mail you're sending. Mail to a deleted or mistyped address is silently ignored, not bounced — double-check the exact address.

The Companion extension shows as offline

Open Settings → Devices and confirm your browser is listed. If it shows offline, sign in to the Cheqq web app again in the same browser — pairing re-syncs automatically and doesn't need a separate code. If the device is no longer one you use, remove it from the same page.

The document editor won't let me close without saving

"Backed up" in the save-status indicator means your edits are captured in version history, not that the live document has your changes. Select Save (or Cmd/Ctrl+S) explicitly, or choose Save and close in the prompt, before navigating away.

A page or workspace looks stale

Navigate away and back once to refresh the current view. If the issue continues, preserve the error text and the action that produced it before contacting Support.