Zapier Table filter using cached test data for "old" values during live runs instead of dynamic live data

I'm running into an issue where a live Zap run is evaluating old test data from my editing session instead of dynamic live data, causing my filter step to fail.

The Setup:

• Step 4: Zapier Table: Update Record

• Step 5: Filter conditions comparing New data vs Old data (e.g., Pick Up Location (new) does not match Pick Up Location (old)).

The Issue:

• In the Editor: When editing and testing the Zap, the test payload correctly identifies the updated vs old values.

• In Live Runs: When the Zap runs live, the Configure tab shows the mapped fields correctly, but under Run Details, the filter evaluates the static test sample (303 Center ave, Janesville, WI) from when I was editing instead of the actual pre-update state from the live trigger.

Because it keeps pulling this hardcoded/cached sample value for the "old" data during live runs, the filter condition is not behaving properly.

Screenshots attached:

1. Live record change payload showing updated fields.

2. Step 5 Configure tab showing the field mappings.

3. Step 5 Run details tab (yellow box) showing the live run falling back to the editor sample data.

Is there a reason Zapier Table triggers don't pass dynamic "old" data in live executions, or am I mapping these fields incorrectly? Any help would be appreciated!