Auto-Refresh Lightning Pages with Salesforce Flow

Introduction

When working with Screen Flows in Salesforce, keeping the page fully up to date can be a challenge—especially when multiple components depend on the same data.

You might update a record using one flow, only to find that another component on the same page still displays outdated information. This creates confusion and breaks the user experience.

This guide walks through a simple and effective solution: triggering a page refresh directly from your flow.

The Problem

In many real-world scenarios:

• Screen Flows are placed on Lightning record pages
• Multiple components (flows, related lists, widgets) exist on the same page
• A flow updates a record successfully

However:

• The updated field reflects immediately
• Other components do not refresh automatically
• Users see inconsistent or outdated data

Example Scenario

Consider a Case record page with two flows:

1. Flow A

• Displays a table of open cases related to a contact

1. Flow B

• Allows the user to update the contact on the case

What happens without a refresh:

• The contact is updated using Flow B
• The record page shows the new contact
• Flow A still displays the previous contact’s cases

Result:

• Data mismatch
• Confusing user experience

The Solution: Page Refresh Flow Action

A custom Flow Action (Lightning component) can be used to:

• Refresh the entire Lightning page
• Reload all components
• Ensure all data is consistent

This works exactly like a manual browser refresh (F5), but is triggered automatically within the flow.

How to Implement

1. Install the Component

Use the appropriate link for your environment:

• Production / Developer Edition
• https://login.salesforce.com/packaging/installPackage.apexp?p0=YOUR_PROD_LINK
• Sandbox
• https://test.salesforce.com/packaging/installPackage.apexp?p0=YOUR_SANDBOX_LINK

2. Add the Action to Your Flow

• Open your Screen Flow
• Add a new Action element
• Search for: ReloadPage
• Select the action

3. Place It in the Flow

• Add the action at the end of your flow

or

• Place it right after a key update step

Key Characteristics

• No configuration required
• No input parameters
• Instantly refreshes the current page
• Re-runs all components and flows on the page

When to Use This

This approach is especially useful when:

• Multiple flows exist on the same page
• One flow updates data used by another
• You rely on dynamic components or data tables
• You want to avoid manual user refresh

Benefits

• Eliminates stale or inconsistent data
• Improves user experience
• Keeps all components aligned
• Reduces confusion and support issues

Conclusion

When building Screen Flows, it is important to think beyond just updating records. Ensuring that the entire page reflects those updates is equally critical.

By adding a simple page refresh action, you can create a smoother, more reliable experience where users always see accurate and up-to-date information—without needing to refresh manually.