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.

Practice typeRealistic client scenario · reviewed credit reward
SubmissionsOpen practice; every contributor can submit their own version
Review outcomePass: +25 Trust Points and +75 withdrawable Circle Credits. Revision or not passed: no points or credits until fixed.
Current statusOpen
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