Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Scheduled tasks cannot access MCP connectors until a user message warms the session (request to reopen of auto closed #35899) [2 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#52977•Fetched 2026-04-25 06:15:43
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Author
eran-medaneran-medan
Participants
eran-medaneran-medangithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×5commented ×2closed ×1

Error Message

Error Messages/Logs

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?

Session ID: session_011uHJWNUcxyRTrpfrwTxDnP

  1. A routine task that used to work now fails, it seems the issue where some tools are not loaded until a user message still happens. (similar to #35899 but I'm not able to reopen it)

  2. What really worried me, is that the links to authorize Notion and authorize GitHub (see screenshot) both led to a Google Drive OAuth screen. but I'll open a separate issue for it...

Relevant part of the session:

<img width="818" height="445" alt="Image" src="https://github.com/user-attachments/assets/5868f9da-3051-4675-8812-b26da26b645d" />

What happens when you click the Notion or GitHub auth links

<img width="1126" height="806" alt="Image" src="https://github.com/user-attachments/assets/c4df998e-a390-480b-9790-17d85bc19001" />

What Should Happen?

  1. Routine tasks should load all connectors successfully, and not wait for user input.
  2. Authentication links to GitHub or Notion should not take you to a Google Drive OAuth screen...

Error Messages/Logs

Steps to Reproduce

  1. Create a schedule routine task with connectors (slack, office, notion, github) in Claude Code Web
  2. Wait a few days
  3. Observe that some tasks are stuck claiming you need to re-authenticate

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

N/A (web)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Reopen request of:

Related to:

  • https://github.com/anthropics/claude-code/issues/48878 (could be related to the Notion auth issue, however it also said it can't connect to github, which is a bit weird as this is a Claude Code routine task, GitHub is the one thing it should have access to, and after the user message, it did indeed admit it does have access to GitHub, the Notion issue might be an additional unrelated issue)

extent analysis

TL;DR

The issue can be mitigated by re-authenticating connectors after a few days to prevent routine tasks from getting stuck.

Guidance

  • Verify that the connectors are properly configured and authorized before creating a scheduled routine task.
  • Check the authentication links for GitHub and Notion to ensure they are correct and not redirecting to a Google Drive OAuth screen.
  • Re-authenticate connectors periodically to prevent them from expiring and causing tasks to get stuck.
  • Review related issues (#35899 and #48878) for potential connections to the Notion auth issue.

Example

No code snippet is provided as the issue is related to authentication and configuration.

Notes

The issue seems to be related to authentication and connector configuration. The fact that the issue is a regression and worked in a previous version suggests that a change in the code or configuration may have caused the problem.

Recommendation

Apply workaround: Re-authenticate connectors periodically to prevent them from expiring and causing tasks to get stuck. This is because the issue seems to be related to authentication and connector configuration, and re-authenticating connectors may help mitigate the problem.

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#tool integration#LLM response#prompt template#agent execution

Still need to ship something?

×6

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

Back to top recommendations

TRENDING