Skip to content

INTAKE FAILED 2026-06-21: M.O.T. connector not attached to scheduled session #1

Description

@rheos

Scheduled intake run failed — action required

Date: 2026-06-21 (UTC ~03:05)
Run type: Scheduled/automated intake routine

What happened

The intake routine started but cannot file any tickets. Two blockers confirmed:

  1. M.O.T. MCP connector tools absentmot_get_ministry_config, mot_list_tickets, mot_create_ticket, mot_update_ticket are all missing from the session's available tools. ToolSearch found no mot_* tools at all.
  2. Direct HTTP to rheo.ca blocked — egress policy returns 403 host not in allowlist. The curl fallback is not usable from the cloud routine environment (as documented in SKILL.md).
  3. PushNotification tool absent — no push notification was sent; this GitHub issue is the only notification channel available.

What was NOT done

  • No snooze-wakeup sweep
  • No Gmail scan
  • No tickets filed or updated
  • No heartbeat ticket filed
  • last_successful_run in mot_get_status has NOT advanced

Fix needed

Re-run the intake session with the M.O.T. connector properly attached. The connector must expose mot_get_ministry_config, mot_list_tickets, mot_create_ticket, and mot_update_ticket tools. Check the session environment configuration at code.claude.com to verify the M.O.T. connector is enabled for this scheduled routine.

Gmail mail from the last 3 days (bills up to 14d) will be picked up on the next successful run via the -label:MOT/Processed filter — no mail will be lost, but nothing has been filed today.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions