Repository navigation
fix(skills): ignite discovery last and treat a failed ignition as blocking - #27
Merged
Merged
Conversation
…cking
On 2026-10-13 a setup agent ran igniteDiscoApi before any shape existed,
saw a complete task, re-ignited several times, and left the tenant's
Discovery API answering 500 for ~2 hours. Ignition now goes last, after
shapes with components and published content. A task that ends in error
is read through info.traces instead of being retried unchanged, and a
{ __typename } probe against Discovery confirms the tenant is serving
before success is reported.
The query reference documents the backend fix landing alongside: a
shapeless tenant has no browse field, and an unbuildable schema answers
TENANT_SCHEMA_UNAVAILABLE.
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
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.
On 2026-10-13 a setup agent ran
igniteDiscoApibefore any shape existed. The task reportedcomplete, the agent re-ignited several times, and the tenant's Discovery API answered 500 for about two hours, with nothing for the agent to self-correct on.The skills now say:
erroris blocking. ReadbulkTask.info.traces, fix what it names, and don't re-run it unchanged. The task query now selectsinfo.{ __typename }against Discovery before reporting success. If it fails after acompletetask, don't re-ignite in a loop; report it.browsefield, and a tenant whose schema can't be built answers 500 withextensions.code: "TENANT_SCHEMA_UNAVAILABLE".Merge after CrystallizeAPI/crystallize#963 is deployed. The ignition refusal and
TENANT_SCHEMA_UNAVAILABLEdescribed here come from that PR. The ordering and probe guidance holds either way.oxfmtwas not run locally (not installed); the one edited table was checked for column alignment.