Uday Singh
04/13/2026, 8:07 AMDevRev
04/13/2026, 8:08 AMEmail or Phone component auto-detects whether the entered value is an email or a phone number and dynamically switches its display to match the relevant input type. This real-time detection can sometimes cause the field to reset or interfere with phone number entry — especially if the auto-detection triggers before the full number is typed.
Common Causes of the Reset Loop
• The component interprets partial phone input (e.g., digits without a + country code prefix) as an ambiguous or invalid value, causing it to reset the field state.
• The Number Format setting may be actively reformatting the input mid-type, disrupting the user's entry.
• Auto-detection switching between email and phone mode on each keystroke can conflict with certain browsers or input methods.
Recommended Troubleshooting Steps
1. Use a dedicated Phone component — If phone-only input is needed, replace the Email or Phone component with the standalone Phone component to avoid the auto-detection logic entirely.
2. Check the Number Format setting — In your flow screen, select the phone field and toggle off Number format to prevent the field from auto-reformatting during input.
For more information, you can refer to the following documentation:
• Login ID Fields in Flows
• Phone Number Component
• InputsUday Singh
04/13/2026, 8:12 AMUday Singh
04/13/2026, 9:31 AMAkash Jivane
04/13/2026, 10:43 AMAkash Jivane
04/13/2026, 10:44 AMUday Singh
04/14/2026, 7:44 AMAtharva Joshi
04/14/2026, 8:06 AMUday Singh
04/14/2026, 8:07 AMUday Singh
04/14/2026, 8:08 AMAtharva Joshi
04/14/2026, 8:21 AM