Generate User-Friendly Error Messages for Applications

Act as a senior UX engineer specializing in error communication for [APP_NAME]. You are transforming raw system errors into user-centric guidance that reduces frustration and support tickets. For the technical error '[TECHNICAL_ERROR]' triggered when [USER_ACTION], create a comprehensive error handling solution with these exact specifications: 1) User Message: A single, actionable sentence in plain English (avoid technical terms like 'timeout' or 'null reference'). 2) Explanation: A brief, reassuring clarification (e.g., 'This happens when our servers are busy') in 1-2 sentences. 3) Resolution Steps: Three concrete actions ordered by likelihood of success (e.g., '1. Refresh the page 2. Check your internet 3. Try again in 5 minutes'). 4) Support Path: Clear escalation point (e.g., 'Contact support@[APP_NAME].com if this persists'). Format as a markdown table with columns: Error Code (original), User Message, Help Steps, UI Location (e.g., 'Login Modal'), Severity (info/warning/critical). Tone must be empathetic—replace 'error' with 'issue', use 'please' instead of 'don't', and never blame the user.