LWC
Refreshing data after a save
Choose the refresh mechanism for the data source.
By Vishal Verma · Reviewed October 5, 2026
Practice these questions aloud. Give the principle, explain a concrete example, and finish with how you would verify the result.
1. When do you use refreshApex?
Suggested answer: For data provisioned by an Apex wire. Retain the wire result object and pass it to refreshApex after the relevant change. It is not a general-purpose page reload.
Scenario / follow-up: Passing only the array of returned records loses the wire configuration.
2. What if Apex was called imperatively?
Suggested answer: Call the loader again when you need a fresh result. If Apex changed records used by Lightning Data Service, use the documented LDS notification mechanism for those record IDs.
Scenario / follow-up: Match the refresh mechanism to the data provider.
3. What should the user see while saving?
Suggested answer: A loading state, prevention of accidental duplicate submission, and clear success or failure feedback. Clear loading in a finally block and keep input available for correction after errors.
Scenario / follow-up: Do not show success before the server operation completes.
Reviewed October 5, 2026. Check the linked documentation for your org’s API version and supported features.