You may encounter a database build failure where a workflow cannot complete because configured column names do not match the fields in the resolved source table. This article explains why this happens and how to resolve it.
What You Might See
A database build or workflow may fail with an error indicating that configured and resolved fields do not align. The message may look similar to:
Failure binding configured inputs to resolved state: configured and resolved fields do not matchThis typically means that one or more field names differ between what is configured in the Source Domain Table and what exists in the resolved state.
Why This Happens
This issue can occur when:
- A Source Domain Table is deleted and recreated
- A column name is corrected, renamed, or modified
- The database schema has not yet refreshed to reflect those updates
- When this happens, the system still references the old field name, while the configuration now expects the new field name, leading to a mismatch and blocking workflow execution.
How to Fix It
To restore a healthy state and complete the workflow:
- Review the Source Domain Table configuration.
- Confirm that the expected field names match the resolved schema.
- If the table was recently modified, reactivate or re-save the updated configuration so the environment rebuilds with the correct field names.
- Regenerate the database and re-run the workflow.
- Once the schema aligns, the database should build successfully and workflows will complete without errors.
Outcome
After correcting the mismatched field name and refreshing the database:
- The schema realigns with the configuration
- The workflow completes successfully
Best Practice
Whenever you rename or correct field names:
- Verify field consistency between configuration and active schema
- Regenerate the database to ensure schemas refresh correctly
- Re-run affected workflows to confirm stability