Fix a scheduled report that errored

Your AI team posts many of its reports from scheduled jobs (cron jobs). When one fails, the agent that runs it posts the error in the report's channel, and the link to that message is all Athena needs to start: she reads the whole thread, then the job's code and logs on your machine.

In this walkthrough, Harbor & Pine's daily store-health report failed validation. Athena found the cause, fixed it, passed the tests and reran the report in eight minutes.

4. Fix a report that errored

4. Fix a report that errored

Copy the link to the failed message#

1. Open the message where the agent posted the error. Here, Nova reports that the daily store-health report was not published.

2. Hover over the message, open More actions (the three dots) and choose Copy link.

   

Ask Athena to fix it#

3. Open #gd-athena-engineering, tag @Athena, say what failed and paste the link. Then say what done looks like. Add the error text if the agent's message cut it short, and anything you already tried. The request from the demo:

   @Athena the daily store-health report failed here: <link to the failed message>
   Find out why it fails validation, fix it the way this box normally ships fixes, rerun the report so it posts, and show me the test results. Keep the report's format the same.

   

Follow the fix#

4. Athena answers in a thread under your message, so the whole job stays in one place. Her status message comes first: the model she is using, the command she is running, and counts of commands and test runs. It says done when she finishes; this fix took 8 minutes and 49 commands.

5. Each test run gets its own reply. In the demo the first run failed because it ran from the wrong folder. The second passed: 28 tests and 5 subtests. A failed run along the way is normal; the last run is the one that counts.

6. Her notes say what she found. Here she confirmed that the old status reproduces the failure and the new one passes, and that her edit to the job was backed up first.

   

7. She reruns the job and checks the result for real: the report posts, or the job finishes without the error.

8. Her answer tags you and says what was wrong, what she changed, the checks she ran and how she shipped it. Here, the job was sending the publisher a QA status it does not accept (ok). She changed it to unavailable, repaired the job's publisher command, and fixed a delivery monitor that was wrongly reporting the report as missing. She shipped the fix through the machine's usual procedure for scheduled jobs, which backs up the job's settings before changing them.

   

9. Open the link in her answer to see the report she reran.

   

When she needs a person#

Some causes are outside the code, such as an expired password or a connection that someone has to sign in to again. Athena stops there and says in her answer what a person or a master admin has to do.