TROUBLESHOOT

Diagnose Grok Bot by symptom, not by random guesses.

Use Troubleshoot as a diagnostic hub: start from what failed, narrow the likely causes, and only then change setup, models, or workflows.

  • 6 symptom-first entries
  • Start from what failed instead of making random guesses
  • Narrow causes before changing setup, models, or workflows

Behavior contradicts the prompt

Bot Ignores Its Instructions

The prompt says one thing, the bot does another. Find which layer is actually in charge.

Report arrives, nobody reads it

Output Not Valuable

The bot runs fine and produces things you never read. Fix the format and the filter, not the schedule.

Something feels off

Quick Health Check

Run this five-minute sweep before you change anything else.

Scheduled output missing

Routine Didn't Run

The 7am report didn't arrive. Diagnose the trigger before the task.

"I don't have access" — or suspicious improvisation

Permission Gaps

The bot says it can't — or worse, works around you. Map what it can actually touch.

Shared bot behaves off-spec

A Shared Bot Acts Strange

You installed someone else's bot and it's doing something odd. Diagnose, then customize or evict.