Start with the visible error, the page you were on, and the action you expected. Preserve completed work before trying a recovery step.
No Access or Agent unavailable
The Member demo received No Access on agent administration and Create Trigger. A compact manager-settings dialog showed Agent unavailable while the manager itself had successfully completed a task.
Check the account, space, agent scope, and exact configuration surface. These messages do not establish that the agent was deleted or that every agent-driven operation is admin-only. A blocked editor and an unavailable tool are separate issues. Ask for the minimum required access; see Roles and access.
An agent cannot create a schedule
Ask which exact capability or permission is missing and whether the proposed work belongs to Home or a project. Current source supports Member-owned agent-created schedules, but the selected agent still needs the relevant tools and allowed target. In the demo, the manager first encountered a capability-approval blocker. After explicit authorization, it created a disabled recurring schedule and read it back successfully. This demonstrates why the exact approval state matters; it does not grant access for unrelated agents or actions.
The demo’s schedule was readable through the agent even though the Member’s Schedules list remained empty. If a known saved record is missing from the list, ask the agent to read that exact record and preserve the discrepancy for support; do not create a duplicate simply to make it appear.
Do not turn a denied capability request into an instruction to use another identity or scope. Obtain the needed authorization or leave the work unconfigured. A quoted plan, due date, or tool schema is not a saved schedule. See Schedules.
An agent request seems stuck
Check whether it is queued in an ongoing conversation, a focused task awaiting review, or a request waiting for input. Ask for the existing item’s state and latest result instead of issuing a duplicate assignment. Delegation and messages explains these distinct states.
The manager ran unexpectedly or did not run
Inspect Dashboard → Objectives → Project flow. A new objective can match its checked initial status even when the creation checkbox is off. Resolving the last blocker can wake the manager independently of the selected status list. Clearing boxes does not cancel queued or active work.
Check Heartbeats, cron schedules, triggers, and scheduled tasks separately. A busy manager, unread queued work, required input, or funding can affect execution. See Project Flow for the Ready retry wording discrepancy; do not assume every Ready objective retries indefinitely.
For a one-time heartbeat, a Completed schedule row means it was handed to a manager-run record, not that execution succeeded. Inspect the actual run and result before creating another copy.
A project or document is missing
- Confirm the signed-in account and selected space.
- Open the expected project.
- Check Data → All resources and search for the title.
- Compare the actual resource with the link in the conversation.
Do not delete or recreate the workspace as a first response. Removing a project association and deleting the underlying resource are different operations.
Branch or rewind is missing
Check the conversation type. The canonical manager conversation in the demo did not show those actions. Persistent conversations and read-only history have different eligibility rules from Flexible chats.
Wait for active work to settle. A visible old message may no longer have the checkpoint needed for the action. See Chats, branches, and rewind before changing history.
Connection problems
Ask the agent to identify the exact missing layer: the connection, provider scope, agent tool access, or a source attached to this space. For missing setup or a connection that needs reconnection, ask it to show the connection card. Use Settings → Connect Apps → Connected as a manual inspection route. A Marketplace card marked Available is not a successful connection.
If no card appears, check the requester’s eligible organization role and the agent’s connection-request capability. The inspected card flow requires an accepted admin/champion requester; the Member demo could not render one. Ask an authorized administrator rather than treating the feature as unavailable or switching identities to bypass a restriction.
After authorization, check the card’s Connected state. A provider success page or closed window is insufficient. Try again is available after a failed request; Cancel resolves an unwanted request. The agent can continue after that response’s cards and questions are resolved.
A healthy connection still needs the relevant tool grant. Custom MCP also requires a verified HTTPS endpoint and the server’s actual auth method; reconnect restores public settings, not secrets. If a selected source is missing from the space, reconnecting the whole account may not solve it.
Record the exact provider error and whether it occurred before or after authorization. Check the intended account and requested operation. Gmail inbox reading is outside the documented Gmail connection scope; Yahoo production availability cannot be inferred from its card alone.
Do not repeatedly authorize broader access or send a duplicate action while the result is uncertain.
An import partly succeeded
Current source supports partial import results. Review created items and per-file or per-row errors before retrying the whole batch. If a sheet was created but not linked, use the supported Add existing route after confirming it exists.
Usage or funding prevents work
Refresh the account’s usage view and read the specific status, allowance, or funding message. A rate window, subscription status, and missing paid balance need different responses. See Plans and usage.
Sign-in or verification link fails
Check the official domain and the original account’s sign-in method. For an expired verification or recovery link, use the current resend or recovery flow when offered. Do not share the link, password, or code in a screenshot.
Prepare a useful support report
Include the time and time zone, page, visible error, account role, expected result, and what you already tried. Add a screenshot only after removing unrelated personal or confidential information. Never include passwords, tokens, or connection credentials.
Use the current official Clero contact information when you need assistance.