So I have an automation rule in JSM that makes 3 web requests. Occasionally in this rule, which all three use the same credentials and call to the same base URL, reports back with a 401 Unauthorized.
I'm staring at three audit rule entries, all three performed the first call but hit 401 on the second. I do not have them setup to proceed on failure so that's where it stops. But three back to back entries where the first call was successful. And the second.. again using the same Authorization header, failed.
I am wondering if there are any like, rate limits or.. well anything in JSM automation rules that might cause this. (I do have a support case submitted with a similar question for the target URL provider)
Thanks!
Since you are doing external calls via the web request then the error would be coming from that external source, not from within Jira. There are limits, but those limits only applies when you make calls to the Jira API, not external APIs.
Thanks! I mean I had this feeling but I needed to ask to cover the bases.
It's still weird though, I can fire off the same call in Postman as quickly as I can click trying to mimic the speed in the automation rule and never encounter a 401.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.