I created a Screen Flow that uses a custom LWC with lightning-record-edit-form to update Contact records. Users can edit multiple fields and click Save. The flow works perfectly on desktop, but on the Salesforce mobile app the record updates don’t persist - the form appears to save but when you navigate away and come back, the changes are gone.
The LWC component includes:
<lightning-record-edit-form object-api-name="Contact" record-id={recordId}>
<lightning-input-field field-name="Email"></lightning-input-field>
<lightning-button type="submit" label="Save"></lightning-button>
</lightning-record-edit-form>
The flow has proper object permissions and field-level security is set correctly. Automated updates fail for our mobile users who need to update contact information in the field. Is there a known issue with lightning-record-edit-form in Screen Flows on mobile?
The lightning-record-edit-form does save data when used standalone in a Lightning page, but inside a Screen Flow you need explicit integration. Add an onsuccess event handler to your form that fires a custom event. The LWC should use @api properties to receive the recordId from the flow and fire an event with the updated field values when save succeeds. The Screen Flow then captures those values and uses an Update Records element to persist them. This ensures consistent behavior across desktop and mobile.
I’ve seen this before. The issue is usually how Screen Flows handle component state on mobile versus desktop. Mobile apps have stricter lifecycle management. Are you storing the record changes in flow variables? The lightning-record-edit-form might be submitting but the flow isn’t capturing the updated values.
There’s a simpler approach if you don’t need custom validation logic. Instead of using lightning-record-edit-form in a custom LWC, use the standard Screen Flow record edit components. Flow Builder has built-in record update screens that work reliably on mobile. The standard components automatically handle object permissions, field security, and mobile compatibility. Only use custom LWC with lightning-record-edit-form if you need custom UI or complex field dependencies that standard flow screens can’t provide.