Skip to content

Unofficial community registry. Not affiliated with, endorsed by, or sponsored by xAI.

中文

Guides

The bot produced nothing

bot-does-nothing

Confirm that it started, then confirm the output path. Do not switch models first.

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: The bot produced nothing
Confirm that it started, then confirm the output path. Do not switch models first.

For: People who ran a task or waited for the schedule and saw no file and no reply.

What to check:
1. Separates “no output” from “it never started.”
2. Checks that the skill name matches what you invoked.
3. Looks for the local file before you swap connectors.

Steps:
1. Look for runs/today.md. If it is missing, save this site's Run receipt skill. Do not look for a built-in run log.
2. If a start line exists, open the output path named in the skill. A missing path means it did not write, or it wrote somewhere else.
3. If the skill never came into play, name it in the instruction. “Use the weekly one” is not a name.
4. Retry with one short instruction and no customer data, password, or secret. Do not send, delete, or pay in order to see output.

Look for runs/today.md. If it is missing, stop and save this site's Run receipt skill:
start <ISO time> <task name>
finish <ISO time> <task name> <ok|error|skip> <one sentence>
If the file exists, search for the task name.
No start line: do not switch models. Check that the instruction was sent.
Start without finish: open the output path named in the skill. If it is missing, write "not written there". Do not invent a success.
Retry instruction (no customer data, password, or secret):
Do not send, delete, or pay.

Do not:
- Do not turn on sending, deleting, or paying just to see output.
- Do not put customer data, a password, or a secret in the retry.
- Do not treat a Grok Bot screen as a run log. Read runs/today.md from this site's Run receipt skill.

Paste this note into Grok Bot and say: follow this note.

What it does

  • Separates “no output” from “it never started.”
  • Checks that the skill name matches what you invoked.
  • Looks for the local file before you swap connectors.

Who it is for

People who ran a task or waited for the schedule and saw no file and no reply.

How to put it in Grok Bot

  1. Look for runs/today.md. If it is missing, save this site's Run receipt skill. Do not look for a built-in run log.
  2. If a start line exists, open the output path named in the skill. A missing path means it did not write, or it wrote somewhere else.
  3. If the skill never came into play, name it in the instruction. “Use the weekly one” is not a name.
  4. Retry with one short instruction and no customer data, password, or secret. Do not send, delete, or pay in order to see output.

Example

Debug note

Look for runs/today.md. If it is missing, stop and save this site's Run receipt skill:
start <ISO time> <task name>
finish <ISO time> <task name> <ok|error|skip> <one sentence>
If the file exists, search for the task name.
No start line: do not switch models. Check that the instruction was sent.
Start without finish: open the output path named in the skill. If it is missing, write "not written there". Do not invent a success.
Retry instruction (no customer data, password, or secret):
Do not send, delete, or pay.

Connectors it needs

No connector.

Safety and permissions

  • Do not turn on sending, deleting, or paying just to see output.
  • Do not put customer data, a password, or a secret in the retry.
  • Do not treat a Grok Bot screen as a run log. Read runs/today.md from this site's Run receipt skill.

Risk: Low

Questions

The reply was empty but the file exists. Is that success?

The write succeeded. Finding it did not. Add the path to the finish line so a person can walk from the log to the file.

How is this different from a hang?

No output means there is not even a finish line. A hang is the interface sitting still. Read the log before you blame the window.