CCR scheduled routine — Google MCP connectors (Gmail, Calendar, Drive) stopped working in remote_trigger environment

Description

A scheduled CCR routine (runs Mon–Fri at 7 AM ET) was working reliably from May 7–20, 2026. On May 21 it stopped firing automatically. Google MCP connectors fail silently with no permission prompts surfaced.

Environment vars observed inside the routine

• CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST=1
• CLAUDE_CODE_ENTRYPOINT=remote_trigger

What we tried

• Re-adding the Google connectors (Gmail, Calendar, Google Drive) — no change
• settings.json allowlist — bypassed by host, no effect
• Runtime "Allow" prompts — never surface in this environment

Key observation

Supabase MCP (native connector) still works fine in the same routine. Only Google connectors fail. Local Claude Code sessions have no issues with the same Google MCPs.

Expected behavior

Google MCP tool calls execute as they did May 7–20 without requiring runtime UI approval.

Routine ID

trig_01AgXyd5VNdWCLD65RkQsCz2