Troubleshooting

NOT_FOUND with registration_tool

Cause: workspace or agent pair not registered.

Fix: call the tool named in the error details (loop_workspace_register or loop_agent_register).

REGISTRY_CONFLICT (409)

Cause: re-registering with different company_name or agent metadata.

Fix: use the existing metadata, or deliberately change via an approved admin path (not silent overwrite).

FORBIDDEN on heartbeat/complete

Cause: workspace_name/agent_name do not own the run_id, or fencing token is stale.

Fix: use the same pair that started the run; refresh fencing from heartbeat/start response.

Validation error missing workspace_name or agent_name

Cause: pre-DEV-28 client calling tools without the pair.

Fix: upgrade skill/runner to pair identity; never use AGENT_LOOP_DEV_*.

loop_self_inspect not found

Cause: tool removed by design.

Fix: use loop_agent_inspect or resource agent-loop://workspaces/{ws}/agents/{agent}.

LeaseHeld / concurrent start

Cause: another run still holds the lease for that agent schedule.

Fix: treat as typed skip; do not start a second run.

Next Steps