Resolving Workflow Failures Caused by Datatype Mismatches in Bridge Connections

Overview

Workflows in Amperity can fail if there is a datatype mismatch between a source table and the schema expected in the tenant.
This commonly happens when data is ingested through a Bridge connection and the source schema changes in Snowflake.

A typical error looks like this:

Failure binding configured inputs to resolved state: type mismatches for fields…

Why This Happens

Bridge connections preserve the schema exactly as it exists in the source system (such as Snowflake).

If:

  • A column’s datatype changes in Snowflake (for example, from decimal(9,0) to decimal(38,0)), and

  • The Bridge feed has not been re-synced,

then Amperity continues to expect the old datatype, causing workflows that depend on that table to fail.

Important to note:

  • Datatypes cannot be changed directly inside Amperity for Bridge-ingested tables.

  • CDT transformations run after ingestion and cannot fix schema mismatches at the source level.

Solution: Sync the Updated Schema from the Bridge Connection

Once the correct datatype exists in the source (Snowflake), you can refresh the schema in Amperity.

Steps

  1. Go to Bridge → Inbound Shares in your Amperity tenant.

  2. Locate the affected Bridge connection.

  3. Click Edit.

  4. Review and confirm the detected schema changes.

  5. Click Save and Sync.

  6. Re-run the failed workflow.

This pulls the updated schema into the domain table and resolves the mismatch.

Expected Result

  • The domain table reflects the correct datatypes from Snowflake.

  • Workflows that previously failed due to schema mismatch run successfully.

  • No further changes are required in Amperity once the schema is synced.

Best Practices

  • When a workflow fails with a datatype mismatch, always check the source table first.

  • Apply schema changes in Snowflake before syncing the Bridge connection.

  • Use Save and Sync after any source schema update.

  • Avoid relying on CDT transformations to enforce datatypes for Bridge feeds.

Summary

Datatype mismatch errors in workflows are usually caused by schema differences between Snowflake and Amperity.
Because Bridge connections mirror the source schema, the fix is to sync the updated schema via the Bridge connection after confirming the source table is correct.

This ensures stable workflows and prevents repeat failures.