ISC workflows fails to show failures in UI and SailPoint marks bug as low priority

[angelo_mekenkamp]

Hi all,

We try to get the failed executions of a workflow through the UI.

We go to:
workflows → click one enabled workflow → executions → filter on status=failed → loading → error

The error is caused by an API that the UI is calling with the error: 502 bad gateway error UI

Logged a ticket with SailPoint Support on October 11th 2024 (38 days ago).
On October 16th 2024, SailPoint Support was able to reproduce the issue in our tenant.
On October 18th 2024, SailPoint Support said:

@SailPoint Support

Thank you for your patience with us.
The engineering is aware of this issue and are working on ways to fix this.
I will keep you posted over the progress.
In the interim, we would request you to kindly bear with us.

I got the exact same message multiple times until November 5th 2024, when I got this:

@SailPoint Support

We have had a feedback from our engineering team, this is a known issue when there are too many workflow executions present.
As per the engineering team, the fix for this may require redesign and is tracked via PLTWRKFLW-5048.
For now, there is no estimated ETA on this, I would suggest you to kindly get in touch with your CSM for any queries related to ETA for the delivery of this.
As no further action is needed, we will shortly be archiving this case from the support end.

I responded the same day with these questions:

@Angelo Mekenkamp

What are too many executions?
Is this only for executions that are currently running or for past executions in total?
When was this ticket PLTWRKFLW-5048 created?

Got this response on November 13th 2024:

@SailPoint Support

After checking with the team internally, the problem is if there are too many workflow executions overall, then due to large data size, we start getting 5xx errors in different places.
Also, this will not be tracked via PLTWRKFLW-5048 but with SAASTRIAGE-5224 (This was created on 16th October).
I hope this helps!!
Do let me know in case of any queries or concerns.
If you do not have any further concerns, we will shortly be archiving this ticket.

I just asked what the priority of this internal ticket is and heard it is low priority.

In our production environment, the UI functionality to get the failed executions is broken, and this is labeled as low priority by SailPoint.

Kind regards,
Angelo

[adamian (Andrei Damian Fekete)]

@SailPoint Support

After checking with the team internally, the problem is if there are too many workflow executions overall

So they don’t know exactly how many is too many?
@angelo_mekenkamp, how many executions do you currently have?

Is there a summary of known limitations and issues for the workflows functionality?

Will the old executions get deleted?

Workflow log retention

Hi there How long do the execution logs for workflows last for? Will they expire at any point and disappear? Thanks Jon

I’ve also seen the issue where some executions disappeared, and SailPoint support wanted a list of them :))

Unable to cancel workflow executions?

Hi Colin, But I do see a cancelled execution in the following case: [image] cancelled workflow executions do not show up on the UI and is the designed behavior I’m confused now. Is it a bug because I do see a cancelled execution flow although SailPoint says it is designed not to show cancelled execution flows? Or is it a bug that some other workflow executions went missing and SailPoint answered incorrectly that this is normal and it is by design? Or is it that in the case of workflow …