Issue
If a Stitch service is disrupted or unable to handle a particular event, we will surface a “Something went wrong” page to the user inviting them to retry their action.
Alternatively, on older SSO variants a user may be presented with a 500 error code page. An example is below 👇
Troubleshooting
As mentioned above this may happen for a number of reasons.
1. Device incompatibility (older and cheaper models outside of ES6 support)
2. Unhandled exception by Stitch
3. Intermittent service disruption by a particular bank
For all methods above we ask that you Retry the action.
If the above fails feel free to contact Stitch support using the form here 🧑🏿💻
Comments
0 comments
Article is closed for comments.