"There was an unexpected internal" Error - 400 Bad Request Error with the /interact Endpoint

This article provides a reason that could cause the following error, which appears to the user as a 400 error with the /interact endpoint.

There was an unexpected internal error. Please try again



 

• There was an unexpected internal error
• Deactivating app
• 400 error for /interact
• Okta Identity Engine (OIE)

The application may encounter a 400 Bad Request with the /interact endpoint in the network logs in the browser console because it provides a clientId of an app that has been deactivated in Okta Dashboard in Applications > Applications.
 

Reports > System Logs will not show errors as the application is deactivated.

To resolve this issue, reactivate the application if it has not been deleted under Applications > Applications > INACTIVE > Activate or create a new application under Applications > Applications and use its clientId in the source code.