Repository navigation
feat(orchestration): report failed runs to the platform webhook and fix job write sets - #1441
Merged
Merged
Conversation
A build that loads a managed source for a selected model now claims that source in its frozen write set, so the worker no longer refuses the run. Group children compute their own write sets, and reruns recompute writers for their narrowed selection. A job that builds a node itself, such as a function its models share with another layer's job, no longer waits for that node's other builders, so tag-selected layer jobs stop reporting a false group cycle. A real cycle now names the group and the edges that close it. Locations and workers warn once per process when a bearer token would travel over plain HTTP to a non-loopback server.
A failed or partial run now publishes a run_failed platform event naming its job, run, location, target, outcome and first failed nodes, with node error text redacted and bounded as for person reads. It reaches only the platform webhook, never person platform history, because error text can quote warehouse data. The server page documents the webhook stream.
Person reads never return run_failed, but the schema's event union now includes it, so the UI history mapping and kind filter drop it.
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 13, 2026
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.
Why
Changes
--no-load-sourcesclaims none; ad-hoc permission checks cover them.http://server gets one warning per process; HTTP stays accepted, loopback silent.run_failedplatform webhook event (same envelope,Idempotency-Key, at-least-once). It names the job or ad-hoc run, run ID, location, target, outcome and up to 20 failed nodes; error text is redacted and capped. Sent forfailedandpartialruns, which have failed nodes. It stays out of person history, as error text can quote warehouse data.Verification
run_failedper partial run through faults and retries, and a group rerun with a loaded source.planned writer source:raw_orders is outside the frozen run write set. The warning shows for 0.0.0.0, not 127.0.0.1.edge_cases/orchestration/shared_function_layers.py. The warning and webhook event have no project shape.make check-ci; UI check, tests and build.