<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D5WR00001rRroL0ASOkta Classic EngineAuthenticationAnswered2026-07-10T14:58:08.000Z2026-07-08T07:30:45.000Z2026-07-10T14:58:08.000Z

YaprakÖ.10821 (Customer) asked a question.

July 8, 2026 at 7:30 AM
Something Went Wrong" Error When Adding User to App

Hi all,

We're experiencing an issue when assigning a specific user to an application in Okta, and hoping someone in the community has run into this before.

Steps to Reproduce:

  1. The user is assigned to the application in Okta.
  2. The user attempts to log in / access the application.
  3. The user is redirected to the browser for verification.
  4. The browser displays "Account verification completed."
  5. However, the application itself shows the error: "Something went wrong, please try again."
  6. The user is unable to complete login to the application at any point.

System Log Findings:

In the Okta System Log, we can see an event titled "Authentication of user via MFA" with the outcome status ABANDONED for this user during the affected time window.

Impact:

The affected user cannot log in to the application at all, blocking their access completely.

Question:

Has anyone encountered this "ABANDONED" MFA status before? What typically causes this, and how did you resolve it? Any pointers on additional logs or configuration checks we should look into would be greatly appreciated.

Thanks in advance for any insight!

  • 1 answer
  • 15 views

  • Paul S. (Okta, Inc.)

    Hello @YaprakÖ.10821 (Customer)​ Thank you for posting on our Community page!

     

    In the Okta System Log, an event with eventType eq "user.authentication.auth_via_mfa" and an outcome of ABANDONED means the authentication attempt was interrupted or timed out before completion. Okta records this when a user is prompted for a multi-factor challenge but fails to satisfy it within the system's allotted timeframe, resulting in no session being granted.

     

    Given that the browser displays "Account verification completed" but the application throws an error and the log shows ABANDONED, the issue lies in the handoff between the authenticator, the browser, and the Okta service.

    • Timeout/Latency Discrepancies: The user may be approving the prompt (e.g., Okta Verify Push) locally on their device, triggering the browser's "verification completed" message. However, if there is a network delay and the approval reaches Okta after the authentication request has already expired, Okta logs it as abandoned and denies access to the app.
    • Browser and Redirect Interference: Strict privacy settings, aggressive pop-up blockers, or third-party extensions can block the final authentication token from successfully redirecting back to the application. The browser completes the local challenge, but Okta never receives the final verification, causing the session to time out.
    • Layered Authentication Policies: The user may have successfully passed your global Okta sign-on policy, but the specific application might have a stricter app-level authentication policy. If the app prompts for an additional factor that fails to render correctly or gets interrupted in the browser, the attempt is logged as abandoned.
    • Time Sync Drift: If the user is using a Time-Based One-Time Password (TOTP), significant clock drift on their mobile device or computer can cause the token to be invalid upon submission, sometimes resulting in a silent failure or abandonment if the user closes the window.

     

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best

  • Paul S. (Okta, Inc.)

    Hello @YaprakÖ.10821 (Customer)​ Thank you for posting on our Community page!

     

    In the Okta System Log, an event with eventType eq "user.authentication.auth_via_mfa" and an outcome of ABANDONED means the authentication attempt was interrupted or timed out before completion. Okta records this when a user is prompted for a multi-factor challenge but fails to satisfy it within the system's allotted timeframe, resulting in no session being granted.

     

    Given that the browser displays "Account verification completed" but the application throws an error and the log shows ABANDONED, the issue lies in the handoff between the authenticator, the browser, and the Okta service.

    • Timeout/Latency Discrepancies: The user may be approving the prompt (e.g., Okta Verify Push) locally on their device, triggering the browser's "verification completed" message. However, if there is a network delay and the approval reaches Okta after the authentication request has already expired, Okta logs it as abandoned and denies access to the app.
    • Browser and Redirect Interference: Strict privacy settings, aggressive pop-up blockers, or third-party extensions can block the final authentication token from successfully redirecting back to the application. The browser completes the local challenge, but Okta never receives the final verification, causing the session to time out.
    • Layered Authentication Policies: The user may have successfully passed your global Okta sign-on policy, but the specific application might have a stricter app-level authentication policy. If the app prompts for an additional factor that fails to render correctly or gets interrupted in the browser, the attempt is logged as abandoned.
    • Time Sync Drift: If the user is using a Time-Based One-Time Password (TOTP), significant clock drift on their mobile device or computer can cause the token to be invalid upon submission, sometimes resulting in a silent failure or abandonment if the user closes the window.

     

     

    Thank you for reaching out to our Community and have a great day!

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best

Loading
Something Went Wrong" Error When Adding User to App