[BUG] Log Persistence Mode Expression Timing

[sfmskywalker]

Log Persistence Mode expressions are evaluated at commit state instead of immediately after activity execution. This leads to issues where:

• Expressions rely on the latest variable value rather than the value during activity execution.
• Activity contexts and execution records are mismatched at evaluation.

Problem

Workflows using dynamic variables face incorrect log persistence decisions because:

• Expressions use the wrong variable value.
• Activity logs do not match their execution context.

Steps to Reproduce

1. Create a workflow with activities and a Log Persistence Mode expression using a workflow variable.
2. Update the variable between activity executions.
3. Observe that expressions evaluate the variable’s latest value, not the value during execution.

log-persistence-issue.json

Expected Behavior

Expressions should evaluate immediately after activity execution to reflect the correct variable state.

Suggested Fix

Update the workflow runner to evaluate Log Persistence Mode expressions after each activity executes instead of at commit state.