Previously working workflow giving HTTP 401

Hi Experts -
We have a workflow which was working perfectly fine till last year and has started to fail recently with the error -
unable to exec HTTP request: Post “https://anzbupa-sb.sds.services.infra.identitynow.com/search/v3/search?limit=250&number=false&offset=0”: request failed with status 401 (type: HTTP Response Returned a Client Error, retryable: false): unable to exec HTTP request: Post “https://anzbupa-sb.sds.services.infra.identitynow.com/search/v3/search?limit=250&number=false&offset=0”: request failed with status 401

Since HTTP 401 is unauthorized, we have generated new access token and re-configured the trigger as well but still it seems to fail. If anyone else faced similar issue or any ideas on how it can be resolved will be highly appreciated.

Regards,
Adi

Hi Aditya!

Is your client still an active client? Are you able to generate a valid JWT token using postman ?

Thanks,
Shailee

Hi there!

Are you blocking any countries geographically in your tenant?

Hi Shailee and Sebastian - Thanks for your replies. To your Qs -
1 - Yes its an active client, we are able to make API calls via postman to the tenant.
2- No we are not doing any geo-blocking.

We found a fix (kind of) by cloning the same workflow to a new one and that is working now. But the old one still fails, we have disabled it now.
Thanks again for all the advise :slight_smile:

2 Likes