FAQ: Pipelines

Tip: Looking for the step-by-step path? Start at the Pipelines overview.

What do the statuses mean?¶

Mapping In Progress means you are still designing, or you changed something after finalizing. Finalized means the destination schema was last built from the current mappings. Editing mappings, keys, strategies, or calculated-column handling in the mapping editor sets a finalized Pipeline back to Mapping In Progress.

Why is Finalize greyed out?¶

Either your organization is read-only, or you have not run Validate without errors since opening the editor. Click Validate, fix the errors, and Finalize becomes available. See Validate a Pipeline.

Where do I configure a load strategy?¶

On the destination schema’s Pipeline tab. The mapping editor lets you pick a strategy, but the configuration dialog, Analyze All, and code generation live on that tab. See Choose a load strategy.

Does Finalize generate the load procedures?¶

No. Finalize builds the destination tables and columns. You then generate the load code from the destination schema’s Pipeline tab. See Generate the load procedures.

Does Kenseme run the load for me?¶

No. Kenseme never connects to your database to create tables or move data. You deploy and run the generated scripts. See Run the generated load.

Which databases can I generate load code for?¶

SQL Server and Fabric Warehouse (stored procedures), and Databricks and Fabric Lakehouse (PySpark functions in a notebook). PostgreSQL, MySQL, Snowflake, and Redshift destinations can be mapped and finalized, but load generation is not supported yet.

When do I need to regenerate?¶

Whenever a table’s status on the Pipeline tab shows Stale. That happens after you change its strategy, configuration, columns, keys, or calculated-column handling, or after a sync removes a column. Kenseme does not regenerate automatically.

I can’t find the generated procedures in the destination schema.¶

They are hidden by default. On the Procedures, Scripts, or Views tab, tick Show Generated.

My source schema changed. What now?¶

Click Sync from Source in the mapping editor. It adds new tables and columns and flags removed ones as stale. Then resolve the stale mappings, validate, finalize, and regenerate, or click Re-finalize to do the first steps in one go. See Keep a Pipeline in sync with its source.

Should I use Sync or Re-run?¶

Use Sync from Source to pick up source changes; it keeps your edits. Use Re-run to change the name, conventions, database system, sources, or table selection. Re-run resets destination table names and key columns you set by hand. See Re-run or roll back a Pipeline.

How do I undo a finalize?¶

There is no undo button. Roll the destination schema back to an earlier version, or generate a migration script between versions and run it in your database. See Re-run or roll back a Pipeline.

What happens to the destination schema if I delete a Pipeline?¶

It stays, with its tables and any generated objects. Only the Pipeline’s mappings and configuration are removed.

Can AI name my destination columns?¶

Yes. Add documentation and run Run AI Rename, then accept or reject each suggestion. See AI in Pipelines.