When a routine looks like it never ran
silent-routine-failures
No error is not the same as a finished run. Check whether a start line and a finish line both exist.
for Grok Bot · unofficial, not affiliated with xAI
CNPS0.1.02026-11-18New
Paste this note into Grok Bot and say: follow this note.
Note: When a routine looks like it never ran
No error is not the same as a finished run. Check whether a start line and a finish line both exist.
For: People who set a routine and found nothing the next day.
What to check:
1. Splits “nothing happened” into three cases: it never started, it returned early, or it finished and wrote somewhere you are not looking.
2. Treats a run as failed when the start line and the finish line are not both there.
3. Sends you to runs/today.md from this site's Run receipt skill before you rewrite the prompt.
Steps:
1. If runs/today.md is missing, save this site's Run receipt skill first. Do not look for a built-in run log screen.
2. Search runs/today.md for the task name. If there is no start line, check whether you sent the instruction. Do not assume a scheduler badge.
3. If there is a start and no finish, add a rule at the end: always write a finish line, including the reason, on success or failure.
4. Run it once by hand and confirm start and finish land in the same file.
Routine name:
runs/today.md exists (if not, save Run receipt first):
start line present:
finish line present:
If only a start, the output path named in the skill:
That path exists now:
Do not send, delete, pay, or write a secret.
Do not:
- Do not treat a Grok Bot screen as a run log. The lines are in runs/today.md, and only after you save this site's Run receipt skill.
- Do not paste mail or customer records into a public place while you debug.
- Do not use this guide to send, delete, or change live configuration.
Paste this note into Grok Bot and say: follow this note.What it does
- Splits “nothing happened” into three cases: it never started, it returned early, or it finished and wrote somewhere you are not looking.
- Treats a run as failed when the start line and the finish line are not both there.
- Sends you to runs/today.md from this site's Run receipt skill before you rewrite the prompt.
Who it is for
People who set a routine and found nothing the next day.
How to put it in Grok Bot
- If runs/today.md is missing, save this site's Run receipt skill first. Do not look for a built-in run log screen.
- Search runs/today.md for the task name. If there is no start line, check whether you sent the instruction. Do not assume a scheduler badge.
- If there is a start and no finish, add a rule at the end: always write a finish line, including the reason, on success or failure.
- Run it once by hand and confirm start and finish land in the same file.
Example
Four lines to fill in
Routine name:
runs/today.md exists (if not, save Run receipt first):
start line present:
finish line present:
If only a start, the output path named in the skill:
That path exists now:
Do not send, delete, pay, or write a secret.Connectors it needs
No connector.
Safety and permissions
- Do not treat a Grok Bot screen as a run log. The lines are in runs/today.md, and only after you save this site's Run receipt skill.
- Do not paste mail or customer records into a public place while you debug.
- Do not use this guide to send, delete, or change live configuration.
Risk: Low
Questions
The time passed. Why is there still no result?
This site does not treat a status badge as the result. Open runs/today.md. No finish line means it is not done. If the file is missing, Run receipt is not saved yet. Grok Bot does not hide another log for this skill.
Should I add an alert first?
Write the finish line first. An alert has nothing to say until that line exists. See Failure note for the alert itself.
0.1.0
2026-11-18
First published text. No usage count.