[BUG] Claude Tag recurring trigger fails with session_config_rejected — dead environment id auto-assigned

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?

Account: 5ae4f5b0-220a-43ac-9d22-fa74358fbd45 (Carlos Andrioli's Claude-in-Slack account)
Workspace: T08S7T0KX, channel C05NH6C5M9S (#team-capital-platform-products-engineering)

Issue: Any recurring trigger created for this account fails to fire with failed to fire trigger: The request is invalid. (session_config_rejected). Reproduced live, repeatedly.

Root cause found:
create_trigger auto-assigns environment id env_011111111111111111111119 to the job config regardless of binding mode (create_new_session_on_fire or self-bind to an existing persistent session). This environment id does not exist.

The account's one visible real environment, env_011RX9qLFohi1hGKQweNPdTK ("Default"), is rejected when explicitly supplied at trigger creation: Environment env_011RX9qLFohi1hGKQweNPdTK does not exist — select a valid environment for this routine (environment_not_found).

Persistent session session_01YBvoemNbzHZCZUc186LBXm (the account's self-bind target) carries the same stale/dead environment reference — self-binding a trigger to it returns success (last_fired_at sets) but the job never actually executes (no downstream Slack post / tool activity observed over repeated multi-minute waits).
Binding a trigger to a different, healthy session is disabled org-wide for this workspace (binding a trigger to another session is not enabled for this organization).

Net effect: no environment id or session is available via create_trigger/fire_trigger that produces a working recurring trigger for this account.

Ask: provision a valid environment for account 5ae4f5b0-220a-43ac-9d22-fa74358fbd45, or repair the stale env_011111111111111111111119 reference on session session_01YBvoemNbzHZCZUc186LBXm.

Affected trigger (left in place, unmodified): trig_01JEX5Cxg9M5Eqo9qbrBCqe8 (weekly-support-handover-and-linear-tagging), cron 50 11 2.Ready to send wherever you'd normally route Anthropic support requests — I don't have a way to submit it myself.

What Should Happen?

Creating a recurring trigger for this account should either (a) auto-assign a valid, existing environment id so create_new_session_on_fire can spin up a fresh session per fire, or (b) if self-binding to a persistent session, that session's stored environment reference should point to a real environment — so fire_trigger actually executes the job (runs the prompt, calls tools, posts to Slack) rather than returning session_config_rejected or silently no-op'ing with a last_fired_at timestamp and no observable effect.

Error Messages/Logs

(list_triggers/fire_trigger/create_trigger/list_environments), not from a log file you can browse — I don't have a logs UI to point you at. I quoted the exact error strings above, but let me pull the full raw transcripts (every call + response verbatim) into a file and upload it so you have the actual source, not my summary.

Steps to Reproduce

1. create_trigger with create_new_session_on_fire=true, no explicit environment_id → trigger is created but its stored job config has environment_id: env_011111111111111111111119 (auto-assigned, doesn't exist).
2. fire_trigger on that trigger id →
3. failed to fire trigger: The request is invalid. (session_config_rejected)
4. (Same thing happens on the real cron fire — the trigger just auto-disables instead, ended_reason: auto_disabled_config_rejected.)
5. Retry create_trigger with create_new_session_on_fire=true and environment_id explicitly set to the one environment list_environments shows for this account (env_011RX9qLFohi1hGKQweNPdTK, "Default") →
6. Environment env_011RX9qLFohi1hGKQweNPdTK does not exist — select a valid environment for this routine (environment_not_found)
7. Retry create_trigger self-bound (omit persistent_session_id, omit create_new_session_on_fire) → creation succeeds, fire_trigger returns success and sets last_fired_at, but no downstream effect occurs — checked the target Slack thread repeatedly over 7+ minutes, nothing posted, no tool activity.
8. Retry create_trigger with persistent_session_id pointed at a different, healthy session (session_01Y3Kb87UrcdJa33XKTfyHtS) →
9. binding a trigger to another session is not enabled for this organization. Omit persistent_session_id to bind to the calling session, or set create_new_session_on_fire=true.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

New

Claude Code Version

New (Claude Tag)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Claude Tag running on Slack