Flow Designer state update is not reflected on the form until page refresh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
When the Flow Designer updates the record state from Draft to Review, the flow completes successfully and the record is updated in the database. However, the updated state is not consistently reflected on the form immediately. In most cases, the user must manually refresh the page to see the latest state. Occasionally, the state updates automatically without a refresh.
Why the UI is not consistently reflecting the state change and ensure the form refreshes automatically after the Flow Designer updates the record
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hey @Sathwik1 ,
This behavior is fairly common when a Flow Designer updates the same record that a user currently has open. The flow runs server-side and updates the database, but the client form doesn't always receive a notification that the record has changed, so the UI may continue displaying cached values until it's refreshed.
A few things to check:
- How is the Flow triggered? If it's asynchronous (e.g., after update, event-based, or delayed), the form won't automatically refresh when the flow completes.
- Check whether UI Policies, Client Scripts, or Workspace behaviors are affecting the State field or overriding the displayed value.
- Verify whether the issue occurs in Classic UI, Workspace, or Service Portal, as each handles record refreshes differently.
- If users need to see the updated state immediately, consider using a client-side mechanism (such as a Client Script, Workspace client action, or g_form.reload() where appropriate) to refresh the form after the server-side update.
- Also review whether there are Business Rules or other Flows updating the same record, as multiple updates can sometimes result in inconsistent UI behavior.
In general, Flow Designer updates do not automatically trigger a form refresh. If immediate UI synchronization is a business requirement, you'll typically need to implement an explicit client-side refresh or use a UI mechanism that listens for record changes.