Retry apply-schema after a cold-start timeout - #43
Merged
ralyodio merged 1 commit intoSep 9, 2026
Conversation
…dio MCP. An idle hosted board can miss a 15s GET, then answer in about a second. Agents that treat that as a dead endpoint skip applying. The CLI now retries GET once on timeout, and stdio MCP reports the real create status so apply_to_job no longer fails after a successful write. Fixes profullstack#36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apply-schemafrom India missed 15s, then answered in ~1.4s). POST is not retried.apply_to_job/post_job/post_updatefail after a successful write./docs,llms.txt, OpenJob, and MCP tool text so agents that are not using this client still retry once.Fixes #36
Test plan
node --test test/client.test.tsafterpnpm build(GET retries once on timeout; POST does not; 201 is preserved)agenticjobs schema <slug>against an idle hosted board still returns the schemaapply_to_jobreports success after a 201 from POST/apply