Get your connection working
Resolve common agent access, tool readiness, Engine connectivity, and execution errors.
Start by confirming the workspace, client grant, and Engine status. Preserve the original job ID and idempotency key while investigating a pending or ambiguous operation.
Agent sign-in or consent fails
agent_grant_required means the client needs a valid grant. Redo OAuth, select one workspace, and complete consent using the account that should access that workspace.
For agent_integration_disabled, an owner may have revoked the client or disabled the feature. Ask the workspace owner to check Agent connections.
An expected tool is missing
tool_not_found can mean that the exact binding is unready, drifted, unapproved, or outside your grant.
Check that:
- The intended Engine is online and advertises the required capability.
- The system connection is active and uses its reviewed connector digest.
- The tool binding is ready and the owner has approved it.
- Your role and client grant permit that tool.
Search the catalog again after an owner resolves the underlying issue. Do not guess a hidden tool key.
Engine is offline
For engine_offline, restore the Engine's outbound control-plane connection. Check the host runtime and the platform's last-heartbeat display, then verify the target system through its connection.
Continue polling an existing job by its original ID. Repeated submissions with new keys can issue duplicate reads.
A request is rate limited
tool_rate_limited, client_rate_limited, user_rate_limited, and tenant_rate_limited identify the affected scope. Wait for the one-minute window before retrying. Keep the same key for the same logical request.
A live operation needs an entitlement
entitlement_required means the trial or subscription does not permit that live operation. Ask an owner to review the workspace's billing and enabled features.
A draft changed while you were editing
For draft_revision_conflict, reload the current draft, reconcile your changes, and submit against the latest expected revision. Reuse an idempotency key only for the same logical request.
An answer has partial or stale evidence
Read the returned observation time, freshness, warnings, and coverage gaps. Missing telemetry, ambiguous identities, or unavailable capabilities should remain visible in the answer.
An expired result does not automatically launch another collection. Make a deliberate new request when you need a new observation and have the required access.
Ask for help
Contact support@convergesense.com with the client name, error code, time of the failure, and safe request or job IDs. Keep credentials and raw customer or equipment output out of messages and public issues.