Documentation

Every Recipe moves through three simple stages:

New

• This is your starting point—anytime you create or copy a Recipe it’s “New.”
• In this state, you can rename the Recipe and change its target table name. Once you build or run it, those names lock in.

Staging

• After you “Run and Save” for the first time, your Recipe becomes “Staging.”
• Staging tables hold up to 60 days of data—enough to preview and tweak your transformations without touching production.
• You can safely experiment here; it won’t affect your live data.

Production

• Click Activate on a successfully built Recipe to move it into Production.
• Production tables have no 60-day limit, so they can store your full data history.

Why This Matters

• Zero risk to live data: All experiments happen in Staging.
• Flexible loading: Staging for previews, Production for full history.

How It Works

Follow these steps to manage recipe statuses effectively:

Step 1. Build Your Staging Table

1. Create a Recipe — it starts as New.
2. Add transform steps (for example, Blend data).
3. Preview your data right away, without building.

4. Click Run and Save to build the Staging table.
5. Watch the status change to Staging.

Step 2. Set Up a Load to Your Destination

1. In the Recipe editor, click + Add Load.
2. Pick your destination—only “Active” destinations are clickable (any in “Error” status will be locked).

3. Optionally, rename the destination table.
4. Click Create Load.
5. Once your load shows up, click Run Load.
6. Choose a date range if needed, then run the load.

7. The “Loading” process will be highlihted while data moves.

Step 3. Fix Errors or Tune and Retry

1. If building or loading fails, you’ll see a Failed status and an error message.

2. Make your edits, then click Run and Save again.
3. Repeat until your staging build and load both succeed.

Step 4. Activate to Production

1. When your Staging version meets your needs, click Activate.
2. The Recipe shifts to Production — no more 60-day limit.

{%docs-informer info %}

• Loads are not created automatically for your transformation tables. You should create it via the transformation wizard and run the historical data load (it will be started only if the table structure was updated).
• Moving a recipe to Staging mode is safe — any ongoing data loads will continue running based on the last Active version. You can freely modify the Staging version without affecting the current operations.

{%docs-informer-end%}

Use Cases

Testing New Transformation Logic

If you want to modify a complex transformation recipe that's currently in production:

• Create a Staging version of the Active recipe.
• Make and test changes without affecting the production data flow.
• Once satisfied with the changes, you can activate the new version and enable the load.

This allows safe experimentation while maintaining uninterrupted data processing in production.

Debugging Production Issues

When troubleshooting problems in a production transformation:

• You can move the current recipe to Staging.
• Analyze and modify the transformation logic in the Staging version.
• Test the fixes without impacting ongoing production data loads.
• After confirming the fix, activate the corrected version.

This approach ensures continuous data flow while resolving issues in a safe, isolated environment.

Conclusion

This system makes data management safer and easier by keeping Staging changes separate from live data. This means you can try out changes without breaking anything that is already working, making the whole process simpler and more reliable.

‍