Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Scheduled triggers stuck at "Coalescing..." / "Processing..." — sessions never execute

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error Messages/Logs

Code Example

Session permanently stuck at "Coalescing..." or "Processing..." with no output and "No sessions found" in the sidebar.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Description

Scheduled remote triggers (Routines) create sessions that permanently hang at "Coalescing..." or "Processing..." status. The agent never starts executing. The sidebar shows "No sessions found."

This affects both cron-scheduled runs and manual "Run now" executions.

Reproduction

  1. Create any remote trigger (even a minimal one with no MCP connections)
  2. Run it manually or wait for cron
  3. The session opens but stays at "Coalescing..." or "Processing..." indefinitely
  4. No output is ever produced

Timeline

  • Apr 16 — Trigger created, first run completed successfully
  • Apr 17 (first run) — Completed successfully
  • Apr 17 (second run) onward — Every run hangs at "Coalescing..."
  • Apr 20 — Tested with a minimal trigger (echo hello, no MCP connections, Bash+Read only) → same result ("Processing..." loop)

Trigger configuration

  • Environment: claude-code-default (Anthropic Cloud)
  • Model: claude-sonnet-4-6
  • Source: GitHub repo via sources[].git_repository.url
  • MCP connections tested: Attio, Slack, Notion (but also fails with zero MCP connections)

What I've tried

  • Reverting to the original prompt that worked on Apr 16 → still hangs
  • Creating a brand new minimal trigger with no MCP and a trivial prompt (echo hello) → still hangs
  • Verified all MCP connectors (Attio, Slack, Notion) are connected and active in setting

What Should Happen?

Expected behavior

The remote session should start, execute the prompt, and produce output — as it did on Apr 16-17.

Actual behavior

Session permanently stuck at "Coalescing..." or "Processing..." with no output and "No sessions found" in the sidebar.

Error Messages/Logs

Session permanently stuck at "Coalescing..." or "Processing..." with no output and "No sessions found" in the sidebar.

Steps to Reproduce

Reproduction

  1. Create any remote trigger (even a minimal one with no MCP connections)
  2. Run it manually or wait for cron
  3. The session opens but stays at "Coalescing..." or "Processing..." indefinitely
  4. No output is ever produced

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.98

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

<img width="1456" height="707" alt="Image" src="https://github.com/user-attachments/assets/d12519e8-afab-4f31-9055-43c24af2ab42" /> <img width="1450" height="709" alt="Image" src="https://github.com/user-attachments/assets/058ab52e-d1b0-4342-a905-e6bc637040f6" />

extent analysis

TL;DR

The issue can be resolved by investigating and addressing the potential causes of the session hang, such as issues with the Claude model, MCP connections, or the Anthropic Cloud environment.

Guidance

  • Verify that the Claude model (claude-sonnet-4-6) is functioning correctly and not causing the session to hang.
  • Check the MCP connections (Attio, Slack, Notion) to ensure they are properly configured and not interfering with the session execution.
  • Test the trigger with a different environment or model to isolate the issue and determine if it's specific to the claude-code-default environment or the claude-sonnet-4-6 model.
  • Review the provided images and logs for any error messages or clues that may indicate the cause of the session hang.

Example

No code snippet is provided as the issue seems to be related to the configuration and environment rather than a specific code problem.

Notes

The issue is reported as a regression, and the last working version is not specified. It's essential to investigate the changes made between the working and non-working versions to identify the potential cause.

Recommendation

Apply a workaround by testing the trigger with a different environment or model to isolate the issue and determine the root cause. This will help to identify if the problem is specific to the claude-code-default environment or the claude-sonnet-4-6 model.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Scheduled triggers stuck at "Coalescing..." / "Processing..." — sessions never execute