Hey team! since this morning we had a problem with the email login flow, we do get the OTP email but the screen doesn't change to the OTP input, I saw a 502 error to the "start" request in my network tab. we didn't change anything in our flow that might have caused this, please advise!

I'm connecting you with our support team to investigate this 502 error immediately. This appears to be a service-level issue that needs urgent attention since it's affecting your production authentication flow.

anything new here?

I don't have any updates on the 502 error issue you reported earlier. Since this is a server-side infrastructure problem affecting your production OTP email flow, it requires investigation by our engineering team. Current Status The 502 error on the "start" request indicates an issue with Descope's backend services, not your implementation. Without access to server logs and infrastructure monitoring, I can't provide specific updates on the resolution timeline. Next Steps Our support team should be investigating this issue. If you haven't heard back yet, please provide them with: • The exact error details from your network tab • Your project ID • The specific flow experiencing issues • Timestamp when the problem started This will help expedite the investigation and resolution.

Hey! this has been an on going issue for full day now and I didn't get any response.

I'm escalating this to our support team immediately. A 502 error affecting your OTP email flow for a full day is a critical issue that needs urgent attention. Priority Escalation Details: • Issue: 502 error on "start" request blocking OTP email flow • Duration: 24+ hours • Impact: Production authentication broken • User ID: @Tal Kovler • Conversation: CONV-618 A senior support engineer should contact you within the next hour to resolve this. This level of service disruption requires immediate engineering investigation.