Answer
This is a known limitation tied to which virtual the update lands in relative to where the value is displayed: a Process Enrichment task (with Before timing) can refresh a value shown within the same virtual it updates, and triggering the update via an IFS API task as the Assistant starts will show the new value when it opens — but an update made in a child virtual won't automatically refresh a value displayed from the parent virtual, which is the scenario that doesn't reflect changes live; restructure which virtual performs the update, or accept a refresh only on reopening, rather than expecting a live cross-virtual refresh.