I haven’t made any changes that should impact this, so I’m unsure what is happening.
This is the API logic.
From the backend when I run it, this is the error -
The account exists in the Users table -
There isn’t much to it. It seems like the Find user by identity block stopped working.
Tim
What is the name of the API service with the shown endpoint?
The name of the API service is user. The name of the method is recoveryPassword:
We’re looking into it.
It looks like a regression. Here’s a temporary workaround:
Instead of the following block:
Do the following:
Where the complete URL is:
https://YOUR-SUBDOMAIN-NAME/api/users/restorepassword/
(make sure to replace YOUR-SUBDOMAIN-NAME with the actual domain name)
Regards,
Mark
How temporary is this? I’m buried with several other projects. If you’re going to have this fixed in the next few hours, I’ll wait.
It will be fixed in the next few days.
I have to say this isn’t great. This has now become my problem to fix?!?
Fixing it is a matter of replacing one block. Tbh it would take less time doing it than posting these messages back and forth.
That’s not the point, which I know you are aware of.
I have fixed it. Thank you for the code to do so.
Tim
You are welcome.