Skip to content

Error Reference

Use this reference when Daeda AI shows a user-visible setup, permission, bridge, portal, data, or execution problem.

What it means: the plan needs HubSpot access that has not been granted yet.

Safest next step: use the re-authorization prompt, approve the access only if it matches the intended work, reload the plan, and execute only after the warning is gone.

What it means: Daeda AI cannot confirm the browser extension is connected and ready for bridge-backed execution.

Safest next step: open the extension popup, reconnect if needed, refresh HubSpot, confirm the target portal, and retry only after the extension shows a healthy state.

What it means: the active HubSpot portal, connected portal, or plan target does not match.

Safest next step: stop before execution, open the correct portal, confirm connected portal status, and reject any draft prepared for the wrong portal.

What it means: connected portal data is in one of these states: BUILDING, FAILED, IDLE, PARTIAL, READY.

Safest next step: wait for READY before relying on rich portal context. If the state is FAILED, review the connected portal card and retry setup or contact support.

What it means: one or more operations did not complete cleanly.

Safest next step: review operation results, inspect HubSpot for completed work, and only retry after confirming repeated operations will not create duplicates or unintended changes.

What it means: the requested HubSpot change is not represented by the current supported-action catalog.

Safest next step: ask for a narrower draft that uses supported actions, or complete the unsupported portion manually in HubSpot.