Practice Task

Practice: Triage an Agent connection failure from logs

Use the supplied runtime logs to write a safe triage plan and a short client reply.

Back to practice tasksEnter task room
Practice typeRealistic client scenario · no cash reward
SubmissionsOpen practice; every contributor can submit their own version
Review outcomePass: +30 Trust Points. Revision or not passed: no points until fixed.
Current statusOpen
Practice boundaryRead the exercise here; submit and revise in the task room

The brief is not the submission area

This page gives the customer scenario, source material, deliverables, review criteria, and suggested format. Formal practice submissions, files, revision notes, and review outcomes belong in the task room so each attempt is auditable.

Exercise brief

Use this page to understand the scenario, assumptions, source material, deliverables, and pass/fail criteria before working.

Task room

Submit the completed result, upload supporting files, send clarification messages, and resubmit a new version if revision is requested.

Reusable practice

There is no participant quota. Multiple contributors can submit, and each version is reviewed against the same criteria.

Review record

Outcomes are pass, revision needed, or not passed. Only a passing version earns Trust Points or case-review eligibility.

Client Scenario

What problem are you solving?

A client says their Agent runtime appears offline and cannot receive tasks after a redeploy. They do not know whether the issue is gateway, auth, environment variables, or deployment configuration.

System Context

Use these assumptions

Assume an Agent gateway, a node service, and deployment environment variables. Do not log into the client system or run commands. Reason from the logs and state what safe information you still need.

Source Material

Base your work only on this material

Log excerpt:
10:02:13 gateway connected
10:02:15 auth token expired
10:02:16 reconnect scheduled
10:02:46 reconnect failed: missing OPENCLAW_NODE_ID
Deliverables

What to submit

  • Most likely cause categories
  • Facts already established by the logs
  • Missing diagnostics or screenshots
  • Safe check order
  • High-risk operations you would not perform without approval
  • A short client-facing reply
Review Criteria

What makes a result pass review

  • Mention both the expired token and missing OPENCLAW_NODE_ID clues
  • Do not ask the client to paste secrets
  • Do not recommend resetting production as the first step
  • Explain the purpose of each check
Submission Format

Recommended format

  • Use sections: judgment, evidence, next checks, risk boundary, client reply
  • The final reply should be understandable to a non-engineer client