[BUG] Routine reports connectors as enabledInChat: false despite being connected globally and attached to the routine

Status Open
Maintainer reply None cached
Activity 3 comments · opened Jul 20, 2026

Preflight Checklist

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

What's Wrong?

I'm hitting a hard blocker on a scheduled Routine (claude.ai/code/routines, "Branch Move Invoice Processor") where the run fails to access its Gmail and monday.com connectors, even though everything appears correctly configured.

What I've verified:

Settings → Connectors shows both Gmail and monday.com as "Connected" (green checkmark) at the account level.
The routine's own Edit routine → Connectors tab shows both Gmail and monday.com attached (2 connectors listed).
I removed and re-added both connectors in the routine's Connectors tab, saved, and re-ran — same result.
Multiple manual "Run now" tests all show status "Completed" in the Runs panel, but the task itself never executes — the routine's own output reports it couldn't reach either connector.
Error detail from the routine's run output:
"Gmail and monday.com are connected at the org level but toggled off ('enabledInChat: false') for this scheduled session, so no tools for either were available."

Expected behavior: connectors shown as attached in the routine's Connectors tab (and connected at the account level) should be usable during scheduled and manual runs.

Actual behavior: both connectors are blocked at the tool-access level before any Gmail search or Monday board action can be attempted, with no way in the UI to fix the underlying enabledInChat state.

Routine is on the "Research preview" version of Claude Code Routines.

What Should Happen?

Expected behavior: connectors shown as attached in the routine's Connectors tab (and connected at the account level) should be usable during scheduled and manual runs.

Error Messages/Logs

Gmail and monday.com are connected at the org level but toggled off ('enabledInChat: false') for this scheduled session, so no tools for either were available.  Both connectors are blocked at the tool-access level before any Gmail search or Monday board action can be attempted, with no way in the UI to fix the underlying enabledInChat state.

Routine is on the "Research preview" version of Claude Code Routines.

Error Message in https://claude.ai/code/session when I run the routine
The Gmail and monday.com connectors are authenticated at the org level but toggled off for this chat session, so no actual Gmail/Monday tools are exposed here — only meta-tools like ListConnectors/SearchMcpRegistry. The routine cannot execute any of its steps (search inbox, read PDF attachments, query boards, send the summary email) without those connectors enabled. This is a hard blocker, not a "found nothing" day, so I'll notify now.

Sent notification
<routine_summary>
Today's Invoice-Later Automation run (2026-07-20) could not execute — the Gmail and monday.com connectors are authenticated for your org but are toggled OFF for this chat session, so no actual mailbox/board tools were available to the routine.

What this means concretely: the run never got past step 0. No search of "Branch Move Invoices" mail was performed, no PDFs were opened, no Monday.com board was queried, and no pulses were created or updated. No summary email was sent to paulandcam@einsteinmoving.com because the mailbox itself wasn't reachable.

This is a session/connector-configuration issue, not a data issue — it will recur on every future run of this routine until fixed. To fix: open this session's connector settings in Claude and enable "Gmail" and "monday.com" for chat (they show as connected/authenticated at the org level, just not enabled in this particular chat context). Once enabled, the next scheduled run should proceed normally.

No other diagnosis was possible since the required tools were never available to inspect the actual inbox or board state.
</routine_summary>

I couldn't complete today's run: the Gmail and monday.com connectors are connected at the org level but not enabled for this chat, so none of the required tools (inbox search, PDF reading, board lookup, email send) were actually available. I've pushed a notification with details. This will keep failing on every scheduled run until those two connectors are toggled on for this session/chat.

Steps to Reproduce

Go to claude.ai/code/routines and click "New routine."
Give the routine a name and a prompt that requires using Gmail and monday.com MCP connector tools (e.g., searching Gmail and creating/updating items on a monday.com board).
In the routine creation form's Connectors section, confirm Gmail and monday.com are both included (they appear by default if connected to the account).
Set a Schedule trigger — in my case, "Runs daily" at a specific time (10:01 PM CDT).
Do not select a repository (leave "Select a repository" unset) — this routine doesn't need one.
Save/create the routine.
Either wait for the scheduled trigger to fire, or open the routine and click "Run now" to trigger it manually.
Open the completed run. Status shows "Completed" in the Runs panel (no infrastructure-level failure), but the run's own output reports that neither connector's tools were actually available, with this specific internal detail: Gmail and monday.com are connected at the org level but toggled off ("enabledInChat: false") for this scheduled session, so no tools for either were available.
Troubleshooting already attempted (issue persists through all of these):

Confirmed in claude.ai Settings → Connectors that both Gmail and monday.com show status "Connected" at the account level.
Confirmed in the routine's Edit routine → Connectors tab that both Gmail and monday.com are listed as attached (shows "Connectors 2").
Removed both connectors from the routine's Connectors tab, saved, reopened the routine, and re-added both via "Add connector," saved again.
Re-ran via "Run now" multiple times after the above fix attempt — same enabledInChat: false result every time.
Expected result: connectors shown as connected (account level) and attached (routine level) should be usable by the routine during both scheduled and manual runs.

Actual result: both connectors are blocked before any tool call can be attempted, with no UI-exposed way to fix the underlying enabledInChat state.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

1.0.0 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="1084" height="880" alt="Image" src="https://github.com/user-attachments/assets/f6414687-2011-4651-a76a-d69103c36901" />
<img width="1898" height="896" alt="Image" src="https://github.com/user-attachments/assets/963f04a4-a4eb-47aa-8c76-ecc8b0720a7c" />

View original on GitHub ↗

3 Comments

Jbansal2 · 1 month ago

Hey! I'd like to work on this issue. Could you please assign it to me? Thanks!

ikasumiwt · 1 month ago

We're seeing the same issue with Slack / Notion / Gmail connectors and found this issue while investigating. Since it doesn't seem specific to Gmail / monday.com, sharing additional data points:

  • Routines that had been running fine on a schedule all stopped working between July 16–17, 2026 (which seems to coincide with scheduled tasks being migrated to Claude Code on the web)
  • Same as described above: runs show "Completed" in the Runs panel, but the run's log reports each connector as connected: true / enabledInChat: false
  • ToolSearch finds no tools for any of the connectors (e.g. query="slack" → "No matching deferred tools found")
  • Re-Creating the routine from scratch, reproduces the same result
michelledineros · 1 month ago

Confirming this reproduces today (2026-07-28) on a scheduled Claude Code Routine.

  • Trigger: trig_0179XN1vqqGytkcdnLjRQuPe
  • Manual run via RemoteTrigger API, session cse_01YQaCTgCJLTrKKL9xLZrbjv
  • Fired 2026-07-27T23:15:35Z
  • Symptom: Slack and Gmail connectors both show as connected/installed in the tool picker, but enabledInChat: false. The session could not discover any mcp__* tools for either connector, aborted before completing its task, and fired a PushNotification instead.
  • This is a recurring weekly routine that has hit this exact failure on at least 3 separate firings (2026-06-29, 2026-07-27, 2026-07-28), so it isn't one-off flakiness.

Secondary note: I also tried working around this by passing a per-run prompt override via the RemoteTrigger API's optional run body. The API accepted it (HTTP 200), but the response only echoes the trigger's stored job_config back — there's no way to confirm from the API response whether a per-run override was actually honored, independent of this connector bug. Might be worth a separate look if per-run overrides are intended to be supported.

Happy to share the full session transcript if useful for triage.