Operations · Intermediate

Monitoring durable workflow executions for retry loops

Inspect orchestration databases for stuck jobs and repeated rate-limit retries before taking action

Use with BotBento Markdown

Opens BotBento. Paste the prompt into a bot; nothing is preconfigured.

  1. On a schedulePeriodic workflow state scan
  2. ThenAnalyze stuck runs and logs
  3. ResultSend triage report for approval

Track long-running orchestration workflows across your database to detect stalled states, crash loops, and backoff failures. When a workflow enters an unhandled retry cycle or hits persistent rate limits, the bot analyzes execution logs, summarizes the bottleneck, and drafts safe restart or cancel instructions for operators.

Prompt to start with

BotBentoRecommended
Check the workflow execution database and recent runtime logs for stalled tasks, failed checkpoints, or repeated backoff errors. When an anomalous job is detected, compile a diagnostic summary detailing the run identifier, error trace, and recommended recovery command. Post the summary to Slack, and wait for human confirmation before executing any cancellation, state reset, or restart commands in the terminal.