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?

Cloud scheduled tasks (claude.ai/code/scheduled) do not have access to MCP connectors. The agent runs ToolSearch for each connector, gets "No matching deferred tools found" for all of them, and concludes the tools aren't available. It then stops and asks the user to connect the MCPs — which are already connected and working.

Sending a user message ("Try again") into the same session immediately makes all connectors available. The task then completes successfully with no changes to configuration. This is 100% reproducible.

This is on a Teams plan, cloud-only. We do not have access to Cowork/Desktop as an alternative.

Environment

• Plan: Claude for Teams
• Platform: Cloud scheduled tasks (claude.ai/code/scheduled)
• Connectors affected: Zoho Cliq (Get_Messages, Post_message), Zoho CRM, Microsoft 365 (Outlook email search)
• Connectors confirmed working: Yes — all work immediately in interactive chat and after any user message in the failed scheduled task session
• Last working run: March 31, 2026
• Broke after: Editing the task prompt and recreating the scheduled task

What I've Tried (none of these fix it)

• Deleted the scheduled task and recreated it from scratch
• Disabled all MCP connectors on the task, saved, re-enabled them, saved
• Simplified the prompt to a minimal test
• Switched models (Sonnet 4.6 → Opus, etc.)
• Swapped prompt content entirely

None of these had any effect. The connectors are simply not in the session's tool registry when the task fires autonomously. A single user message makes them appear instantly.

What Should Happen?

Cloud scheduled tasks should initialize MCP connectors when the session starts, not require a human message first. The entire point of scheduling is autonomous execution.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

1. Connect Zoho Cliq, Zoho CRM, and Microsoft 365 (or any, it would seem) connectors at claude.ai/settings/connectors
2. Verify all work in a normal interactive Claude Code session
3. Create a cloud scheduled task at claude.ai/code/scheduled that calls these connectors as its first actions
4. Let the task fire (or click "Run now")
5. Observe: Agent runs ToolSearch, finds nothing, reports all connectors are unavailable
6. Type any message into the session (e.g., "Try again")
7. Observe: All connectors now work immediately

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude Code Web

Platform

Anthropic API

Operating System

Other

Terminal/Shell

Non-interactive/CI environment

Additional Information

Related Issues

• #35899 — Scheduled tasks cannot access MCP connectors until a user message warms the session — Same bug on Desktop (Datadog/Jira). Labeled "invalid — not related to Claude Code" suggesting this is a platform infrastructure issue.
• #36327 — Claude Code Scheduled Task - MCP/Tool access — Same bug on Desktop (Slack). Closed as duplicate.
• #32000 — Scheduled tasks cannot access HTTP MCP servers — missing user:mcp_servers scope — Zoho MCP servers specifically. Stale.
• #40835 — Creating a new scheduled task disables MCP connectors in existing scheduled tasks — Creating/editing a scheduled task silently disables connectors on existing tasks.
• #40669 — Scheduled tasks with Chrome MCP pause execution until user focuses the task in UI — Chrome MCP tools in scheduled tasks don't execute until user focuses the task.

Workaround Found !

Reddit user /u/e_lizzle was able to identify a workaround that worked for me - it'll cost a few extra tokens but if you start the scheduled task prompt by telling it to not do any work but instead to use an agent to do the entire task - everything works fine because the subagent gets mcp tools initialized properly. Then for now I'm telling it to have the subagent report a summary back up to the primary so I can look at its results in the task log.

Cost difference is probably negligible and it solves the problem until its formally fixed.