Max plan only allows 1 sub-daily scheduled trigger despite $200/mo tier

Problem

On the Claude Max (\$200/mo) plan, attempting to create a second scheduled trigger with any sub-daily cadence returns:

{
  "error": {
    "message": "Your plan gets 1 hourly cloud scheduled session. Disable or delete an existing schedule to continue.",
    "reason": "trigger_limit_reached",
    "type": "invalid_request_error"
  }
}

This limit applies to any cron expression that fires more than once per day — tested and rejected:

• 0 * * * * (hourly)
• 0 */2 * * * (every 2h)
• 0 */4 * * * (every 4h)
• 0 9,13,17 * * * (3 fixed times)
• 0 9,17 * * * (2 fixed times)

Only 0 9 * * * (once daily) works for a second trigger.

Why this matters

On the Max tier users are actively building agentic workflows. A realistic setup:

• Board Sync — runs hourly, moves merged PR issues to \"In Review\"
• Autofix — picks up Ready issues from the project board, creates PRs

Both are lightweight and idempotent. The per-run usage is well within Max's normal session quota. But the plan's hard cap of one sub-daily trigger forces an artificial tradeoff: you either get timely PR board updates OR timely auto-fix runs, but not both.

Request

One of:

1. Raise the limit on Max — e.g. 3-5 sub-daily triggers. This would align with the value proposition of the tier.
2. Document the limit clearly on the scheduled tasks page and the Max plan comparison. Currently the only way to discover the limit is to hit the error.
3. Surface the limit in the UI when scheduling via claude.ai/code — at least show how many slots are remaining.

Related: #40124 covers the documentation aspect. This issue is about the actual limit being too restrictive for the Max tier use case.

Environment

• Plan: Claude Max (\$200/mo)
• Feature: Cloud scheduled tasks via \POST /v1/code/triggers\
• Date: April 2026