propagation-failed

type: https://docs.d2b.dev/errors/propagation-failed — The write succeeded, a downstream rebuild did not. Typical status: 400.

Unlike validation, nothing about your request was wrong and nothing was rolled back. The transform you sent was saved, its output table was materialised, and its bindings and lineage were recorded. What failed afterwards is a separate, already-existing transform downstream of the artifact you just wrote: the eager recompute could not rebuild it against the new output.

Typical cause: the new version of your transform changes the output’s schema (a dropped or renamed column, a changed type) and a downstream transform still reads the old shape.

What to do

• Do not resend the same request expecting a different result — your transform is already stored and materialised. Resending re-runs it and hits the same downstream failure
• detail carries the underlying error from the transform that failed to rebuild. Read it to find which downstream step broke
• Fix that downstream transform (usually: update it for the new schema), then re-run it. GET /api/v1/workbooks/{id}/transforms lists the stored templates, and the lineage DAG shows what depends on your artifact
• The downstream artifact still holds its previous content — the rebuild did not land, so it no longer reflects your new output. Re-run it explicitly once fixed; it is not queued for you

All error types: Reading errors.