Domo Magic ETL failed before dashboard update: task cancelled because input dataset schema changed error

TL;DR

Diff the definition against the live source schema, fix the named field type or reference at its definition rather than at each consumer, and rebuild or revalidate in dependency order. Start in the Domo DataCenter, the Magic ETL canvas, and the dataset history, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.

Domo Magic ETL failed before dashboard update: task cancelled because input dataset schema changed error

Use this when

• You see this exact message or symptom in Domo: Domo Magic ETL failed before dashboard update: task cancelled because input dataset schema changed error
• One run, record, build, or object is affected and you can name it
• A retry without changing anything reproduces the same text

Not for this skill when

• Domo fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once in the Domo DataCenter, the Magic ETL canvas, and the dataset history and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
2. Inspect the Magic ETL input dataset schema, the changed columns, and the output dataset the dashboard reads, and check the schema diff, the corrected field definition, and the validation run that now passes for the whole object. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
3. Apply the fix at that source: diff the definition against the live source schema, fix the named field type or reference at its definition rather than at each consumer, and rebuild or revalidate in dependency order. Verify: the corrected value or setting is visible in Domo itself, not only in a local config file
4. Re-run the original operation on the single affected item first: open the ETL, remap the changed input columns, run it for the current input, then open the dashboard card. Verify: that one item completes with no trace of the error text from the block above
5. Check the downstream result a user or the next job would see: the ETL completing and the card showing the new output timestamp. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed

Variant phrasings

Domo Magic ETL failed before dashboard update: task cancelled because input dataset schema changed error

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.

Domo version of this failure

The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does domo Magic ETL failed before dashboard update: task cancelled because input dataset schema changed error keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.

Compatibility: Domo Magic ETL 2.0, DataCenter datasets and cards. The steps assume you can read the job or build log and change the named object in Domo.

Why it happens

In Domo, this failure usually means the definition and the real data disagree on a field name, type, or dependency, and the engine refuses to guess which one is right. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst6ttZ0hXPJ7PQk64rFihTQ