Troubleshooting

Start by identifying the boundary that failed. Most d5s problems fall into one of five layers: access to the resource, admission of a turn, schedule eligibility, capability authorization, or execution after a run started.

A run will not start

Check the visible session state first.

• If a turn is queued, the session already owns active work. Wait, or cancel the queued turn.
• If the session is active, stop it only when you intend to interrupt the current tool work.
• If an agent is paused or its daily budget is spent, manual and autonomous work can be blocked until resumed or until the next local day.
• If an automation already has a run in flight, its per-automation lock skips another fire.
• If the request is rejected before a session appears, verify workspace access, project access, model policy, and uploaded file ids.

If a workspace is missing from the switcher and its organization appears under Switch organization, select that organization first. If the organization does not appear or the workspace remains missing, ask an organization Owner or Admin to assign you or one of your groups to that workspace. Organization membership and a workspace grant are separate; joining the organization does not grant access to all of its workspaces.

A sandbox id can be empty before the run needs an execution environment. That alone is not a failure; look for the queued, start, sandbox-ready, error, or terminal events.

A connector action is unavailable

Check the connector chain in order:

1. The workspace credential exists and is not archived or awaiting reauthorization.
2. The credential is activated on the session's project. For an agent, inspect the agent's home-project connectors.
3. The requested tool is Allow, an Ask approval is still live, or the session is visibly in Allow all mode.
4. The connector descriptor allows the target host, method, and path.
5. The external account can access the requested object.
6. The provider account has sufficient credits, quota, and feature access for the requested operation.

If an Ask action is waiting, return to the conversation and answer the pinned connector approval card. Approving once does not approve later calls. You can instead switch that conversation to Allow all, which retries the pending action once. If the retry fails, the approval card remains available. If Allow all is not shown or an action still pauses, the feature may be unavailable for the workspace or an explicit Deny or another connector boundary may be blocking the call.

A scheduled run did not happen

For an automation, verify enabled state, trigger kind, timezone, next due time, daily quota, and active-run lock. Recurring missed slots coalesce, so an outage does not generate one run for every missed interval. A one-time occurrence retries until accepted and disables itself after a confirmed fire.

For an agent heartbeat, verify heartbeat enabled state, agent pause, timezone, next heartbeat, last heartbeat status, and daily budget. A busy heartbeat is intentionally skipped. For a task-specific scheduled wakeup, a busy or transiently failed occurrence is retained for retry instead. A one-time wakeup also remains due after a budget skip and retries when budget becomes available.

Remember that Wake now does not move the next heartbeat and Run now does not reset an automation's recurring schedule.

The result looks stale

• A dashboard may be showing the last live version while a new build is active or failed. Open the chat and version menu to inspect both.
• A project file or connector activated after a run changes future runs, not the history of the completed one.
• An agent keeps one long conversation and may compact older context; put durable facts in project instructions, files, or memory rather than relying on a distant chat turn.
• A restored dashboard version becomes live without creating a new agent run.

d5s Desktop is not updating

Settings → Desktop → Updates shows the installed version, a manual check button, and a live status line. Automatic updates download in the background and install the next time you quit the app; there is no setting to turn this off.

• macOS: "Automatic updates are unavailable in this build." This build cannot verify update signatures and cannot install an update even if one is downloaded. Download the latest installer from d5s.tech instead of waiting for it to update itself, and repeat that until this message stops appearing.
• A background check runs at launch and again every few hours; it fails silently so a temporary network problem never interrupts you with an error. Only a manual check (the button in Settings, or "Check for Updates…" in the app menu) surfaces a failure.
• Once a download finishes, the app shows an update-ready card and keeps showing it until you install or quit, even if a later background check runs in the meantime.

Keep the evidence

Before retrying repeatedly, record:

• workspace and project;
• resource type and id;
• session id and turn id;
• scheduled time and timezone, if applicable;
• approximate wall-clock time;
• last visible event or error;
• connector and tool name, without credentials or sensitive content.

Those identifiers let support correlate the UI, audit record, scheduler, worker, and session event log. Never paste API keys, OAuth tokens, connector secrets, or full confidential prompts into an issue.