Skip to content

docs(canary-fleet): correct timeout PUT field name in manifest header - #915

Merged
vybe merged 1 commit into
devfrom
fix/canary-manifest-timeout-field
May 23, 2026
Merged

vybe merged 1 commit into
devfrom
fix/canary-manifest-timeout-field

Conversation

@obasilakis

Copy link
Copy Markdown
Contributor

Summary

  • Manifest header in config/canary-fleet.yaml documented the post-deploy timeout PUT body as {"timeout_seconds": 180}, but the API endpoint PUT /api/agents/{name}/timeout requires execution_timeout_seconds and rejects the request with execution_timeout_seconds is required otherwise.
  • One-character (well, one-field) doc-comment fix so the next operator who copies the recipe verbatim gets a working call.

Caught during

Deploying the slow agent (canary-fleet-slow) on the dev instance via the documented recipe.

Test plan

  • Re-ran the corrected PUT body against dev — execution_timeout_seconds: 180 returns {"message":"Timeout updated","execution_timeout_minutes":3}

The post-deploy PUT body documented in config/canary-fleet.yaml used
`timeout_seconds`, but PUT /api/agents/{name}/timeout requires
`execution_timeout_seconds` (returns "execution_timeout_seconds is
required" otherwise). Caught while deploying the slow agent on dev.

@vybe vybe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved — 1-line doc-comment fix matches the actual endpoint contract in agent_config.py:502. All 12 CI checks green.

@vybe
vybe merged commit 3cc0517 into dev May 23, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants