I think there is currently no standard functionality (including search) to get a daily e-mail notification with a list of failed workflows.
Because of that I want to create a workflow that queries daily a specific workflow for failed executions, and if there are any failed executions present it should send a notification.
I though of using the following API/parameters: {{baseUrl}}/workflows/:id/executions?limit=1&offset=0&filters=status eq "Failed" and start_time gt 2024-04-28T22:00:00.000Z and start_time lt 2024-04-30T22:00:00.000Z
The workflow errors out with the following error: failed to add queryParams to HTTP Request, key value pair not provided when the query parameter value contains a colon ( :).
Hi Andrei. I was not able to reproduce your 502 and 504 errors. Following your examples, I was able to successfully make those API calls. The workflow service may have been temporarily unavailable when you made those calls.
However, I am able to reproduce your key value pair issue when using colons in a query param. I have opened this bug report for you.
If I need to wait for a fix I kind of give up and try to find a workaround. Two weeks ago the “SailPoint support team” closed the ticket opened on second of May (regarding the illegal/unsupported : character) with this answer:
This is with the backend team and they are working on getting the cause and the fix for the same. Here is the JiraID SAASTRIAGE-3159 you can share with your CSM to track the progress of the fix.
Archiving this here from the support end. Have a good week ahead!!
Instead of providing a page where we can see the progress I would need to keep asking the CSM for updates. Who’s got this much time?
To get around this until the colon in query params bug is fixed, you can just put the query params directly in the URL of the HTTP Request. For example, you can configure the Request URL as follows:
Hi, I’m encountering the same issue as Andrei. Whenever I apply the ‘failed’ filter, I consistently get a 502 error, regardless of the time difference I set. As soon as I add the filter, it stops working. There haven’t been any reported issues with workflows, though. It’s frustrating that there’s no retry mechanism, and the suggested workaround isn’t working either.
Using the failed filter alone works, using the date filter alone works, using both filters, wont work.
The 502 (Bad Gateway) is a network related error and shouldn’t be related to your query parameters. Can you reliably reproduce this, or is it intermittent? FWIW, I tried the same query parameters and it works for me.
Hi Colin, i did some test with other workflows, every workflow that has less that 50k executions is able to retrieve the list without issue, over 50k executions gives 502 error, can you confirm if the api has a limit on more than 50k executions using combined filters?
