Bot temporarily unavailable

[worktrunk-bot]

The bot failed to process a request. This issue tracks failures until the underlying cause is resolved.

When	Run	Trigger
2026-08-08T22:24:40Z	workflow run	N/A

This issue was created automatically. Close it once the outage is resolved.

[worktrunk-bot]

When	Run	Trigger
2026-08-08T22:26:36Z	workflow run	#3779

[worktrunk-bot]

When	Run	Trigger
2026-08-08T22:42:51Z	workflow run	N/A

[worktrunk-bot]

When	Run	Trigger
2026-08-08T22:56:48Z	workflow run	N/A

[worktrunk-bot]

When	Run	Trigger
2026-08-08T23:01:32Z	workflow run	#3779

[worktrunk-bot]

When	Run	Trigger
2026-08-08T23:08:37Z	workflow run	N/A

[worktrunk-bot]

When	Run	Trigger
2026-08-08T23:24:41Z	workflow run	N/A

[worktrunk-bot]

When	Run	Trigger
2026-08-08T23:41:57Z	workflow run	N/A

[worktrunk-bot]

When	Run	Trigger
2026-08-08T23:54:56Z	workflow run	N/A

[worktrunk-bot]

Drained. The outage was a Claude session-limit exhaustion spanning 22:23Z–23:55Z on 2026-08-08; quota reset at 00:00Z and every tend-* run since has succeeded, so the underlying cause is resolved and this issue is closed.

Disposition of the nine rows:

Rows	Run(s)	Disposition
7	tend-notifications on schedule	Self-recovering — later cron ticks at 00:12Z, 00:33Z and 01:08Z succeeded. Not re-run.
1	31281595492 — tend-review for #3779	Already recovered by hand: attempt 2 started 00:01:31Z, approved 00:05:35Z, PR merged 00:09:49Z. Not re-run.
1	31282964053 — tend-mention on repository_dispatch for #3779	Genuinely stranded, but the work is moot. Not re-run.

The tend-mention row is the only one that could not self-recover, and it is worth naming why re-running it would be wrong rather than merely unnecessary. Its trigger was the maintainer's inline review reply on #3779 at 22:59:32Z, which accepted the bot's suggestion and reported the change already pushed as 48ba00607. #3779 merged at 00:09:49Z, so a rerun now would post into a merged thread against a resolved comment.

That leaves the tend-review row as the one real loss the outage caused, and it was absorbed by a manual rerun rather than by anything automated: tend-review fires only on pull_request_target, so without that rerun #3779 would have merged unreviewed. Nothing in the current skill set would have drained this issue either — the guidance for it was removed in #3742 pending an upstream PR that has not landed. #3781 restores it.