Summary
When attempting to trigger or enable any scheduled task (agent) in the Amazon Quick desktop app, the operation fails with:
“Cannot save agent ‘[agent_name]’: GMAIL connector [connector_id] is not authorized. Pick a different workspace or reconnect the connector in Settings.”
This occurs regardless of whether the agent uses Gmail tools — even a minimal agent with only core tools in its policy triggers this error.
Environment
- App: Amazon Quick Desktop (Windows)
- Version: Latest as of May 21, 2026
- OS: Windows
Steps to Reproduce
- Have a previously-connected Gmail connector that has since been disconnected/deauthorized
- Create any new scheduled task (even one with no MCP tools — just core group)
- Attempt to trigger the agent with trigger_agent
- Error fires immediately
What I Tried
- Deleted and recreated the agent with no Gmail/Google connector references
- Removed connector_preferences from the agent config
- Created a brand new agent with a different ID — same error, different connector UUID
- Disconnected all connections in Settings → Capabilities → Connections
- None of the above resolved the issue
Expected Behavior
- Agents that don’t reference Gmail in their tool_policy should not be blocked by a stale Gmail connector
- Disconnecting a connector in Settings should fully purge its registration so it no longer blocks other operations
- The scheduler’s connector validation should only check connectors actually used by the agent’s tool policy
Actual Behavior
The system validates ALL registered connectors globally at agent save/enable time, regardless of whether the specific agent uses them. Stale connector registrations persist even after disconnecting in the UI, making it impossible to trigger ANY scheduled task.
Workaround
None found. The stale connector reference persists across agent deletion/recreation and even after removing all connections. App restart also did not resolve.
Additional Context
The connector IDs that appear in the error messages change between attempts (e.g., b9d7c702 on one attempt, 965e815a on another), suggesting multiple stale Gmail connector registrations exist in the system that weren’t fully cleaned up on disconnect.