We are using custom database migration scripts for our tenant. Users are regularly having issues completing the reset password flow as part of their migration and receive the generic “The server cannot be reached, please try again.” but when analyzing the logs it shows the password was changed successfully. It appears that the issue is due to a hard coded 6 second timeout for the request and is cancelled before completing.
Is there any way to increase the timeout to allow for more time for the custom db script to complete?