Workflow Failure Due to Schema Mismatch After Table Column Removal

Overview

This article explains why a workflow may fail when certain fields are removed from a table. The failure occurs due to a mismatch between the workflow’s expected fields and the actual fields in the table.

Issue Summary

The workflow failed with the following error:

Failure binding configured inputs to resolved state: table amperity.domain/ucp_att_cl_sailing_PROD configured schema contains fields dqs, hae, ncc, nch, ncn, and others which are missing from resolved state.

This happened because some fields in the table were removed, but the workflow was still expecting them.

Affected Fields

Workflow failure can occur when fields are removed or changed in the table but are still referenced in the workflow’s configuration. The actual affected fields may vary by case.
Example of affected fields in this case: DQS, HAE, NCC, NCH, NCN, NNC, NRC, Y01, Y29.

Root Cause

The workflow expected fields that no longer exist in the table. This mismatch between the workflow’s configured schema and the table’s actual schema prevented the workflow from running successfully.

In Amperity, this situation is known as “Inputs Unbound.”

What This Means

When a workflow’s expected fields are missing from the table:

  • The workflow cannot bind its inputs properly

  • Database generation or other steps may fail

  • You will see an error indicating which fields are missing

Preventive Recommendations

To prevent similar issues in the future:

  1. Review workflow dependencies before removing or modifying table fields

  2. Update workflow configurations immediately after changing table schema

  3. Validate workflows after structural changes to the table

  4. Refer to Amperity documentation when making database input changes

References