Practice Task

Practice: Triage a scheduled automation that did not run

Use the supplied logs to explain why a daily report email did not send and what to check first.

Back to practice tasksEnter task room
Practice typeRealistic client scenario · no cash reward
SubmissionsOpen practice; every contributor can submit their own version
Review outcomePass: +25 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 should receive yesterday's report by email every day at 09:00. Today no email arrived. They only provided a few log lines, so you need to explain the likely chain and safe next steps.

System Context

Use these assumptions

Assume a cron job, report API, and email service. The deployment could be Vercel, a server, or an automation tool. Do not log into a real system and do not ask for passwords or secrets.

Source Material

Base your work only on this material

Log excerpt:
08:59 cron triggered
09:00 fetch report failed: 401
09:00 email skipped: no attachment
Client symptom: the 09:00 daily report email did not arrive today.
Deliverables

What to submit

  • Most likely cause
  • Facts proven by the logs
  • Information to request from the client
  • Safe check order
  • Temporary workaround
  • Prevention suggestions
  • Short client-facing reply
Review Criteria

What makes a result pass review

  • Explain that 401 can prevent report attachment generation
  • Explain why no attachment leads to skipped email
  • Do not request passwords, API keys, or secrets directly
  • Include a temporary resend suggestion
  • Separate known facts from assumptions
Submission Format

Recommended format

  • Use sections: judgment, evidence, checks, temporary workaround, prevention, client reply