Example error:
Failure binding configured inputs to resolved state: type mismatches for fields <COLUMN_1> (config: decimal(9,0), state: decimal(38,0))
Content
When running a workflow in Amperity, it may fail with an error indicating a datatype mismatch between the source system and the Amperity domain table.
This usually happens when the data type of one or more columns changes in the source system (for example, Snowflake), but the Amperity Bridge connection hasn’t been re-synced to reflect the new schema.
How to Fix
- In Amperity, go to Bridge → Inbound Shares.
- Find the affected feed and click Edit.
- When prompted, confirm the schema change.
- Click Save and Sync to refresh the schema in Amperity.
- Re-run the workflow. It should now complete successfully.
Best Practices
- Always verify the schema in the source system after datatype changes.
- After confirming the change, use Save and Sync in Bridge to ensure Amperity reflects the latest schema.
- Avoid using CDT transformations to fix schema mismatches — they run after data ingestion.
Expected Behavior
Bridge feeds preserve the schema from the source system.
If the source table schema changes (for example, from decimal(9,0) to decimal(38,0)), Amperity must re-sync that schema before workflows can run successfully.
This is expected and documented behavior for Bridge connections.
For more details, see the Amperity documentation on Bridge connections.