E04105 — EmailBlockPublishNewInputsUnconfirmed
Publishing this block makes live templates that use it require new inputs.
- HTTP status:
409 - Type:
conflict_error - Name:
EmailBlockPublishNewInputsUnconfirmed
What to do
The new version of a language reads a value the sender must supply in template.parameters, and live templates link this block in that language, so a send that does not supply it can be refused. The error names each such language's new inputs and up to ten of those templates. A broadcast with language overrides must also supply a default-language input in its base parameters, not only in an override. In the block editor, Cancel keeps the change in draft until senders are ready, and Publish anyway publishes it. The broadcast composer offers the new input only once the block is published, so keep affected broadcasts in draft, publish, then refresh the composer, supply the values and validate each broadcast before sending it. An API caller publishes anyway by repeating the same languages and revisions with confirm set to true, or --yes in the CLI, under a new idempotency key.
Operations that resolve this:
Related
- Idempotency: safe retries and key reuse rules
- E04xxx — Email sending & delivery: every code in this range
- Errors: the full wire contract, status mapping, and error catalog
- Error handling: branching on
typeandcode, validation details, andvendor_code