Computed values not saving into new rows via workflow

Ask for Help
1

Hi all, I’m building a manager-focused planning app.

I have a workflow triggered by a button (“Run & Save”) that:

  1. Runs on the current Sales Metrics row.
  2. Does a Set Column Values step to stage a computed value (Prospecting % Final, an IF/THEN/ELSE number, into a plain number column called Snapshot Staging (num)).
  3. Then creates a New Row in another table (Plan History), where I map Prospecting % (snapshot) in Plan History = Snapshot Staging (num).

When I test in the workflow editor (clicking Run inside the builder), the value populates fine.
When I press the Run & Save button in the live app, the new row is created, but Prospecting % (snapshot) is always blank.

Things I’ve already tried:

  • Replacing the computed field with a staging Number field.
  • Adding a helper Math column to coerce the % into a number.
  • Switching the target column to Text.
  • Confirmed the staging column itself is populated before the Add Row runs.
  • Mapping constants (like 999) do show up in the new table, so the workflow step is firing.

So it seems the issue is with timing / computed → Add Row mappings not surviving at runtime.

Question:
How can I reliably pass a computed number from one table into a new row in another table when creating that row in a workflow? Is there a pattern (e.g. RowID update, relation + Set Column Values, or a known timing workaround) that avoids the blank values?

Thanks in advance!

2

Hi there, the most reliable to ensure data from computed columns is loaded in a workflow is to use wait for conditions to ensure you computed columns are not empty.

Hope this helps :slight_smile:

3

thanks!