Roman Eisner commented on issue #594334 at GitLab.org / GitLab

Roman Eisner
2026-04-14T19:20:00Z

Hey @lindsey-shelton

Just trying to create some scenarios locally.

Here are two examples.

Example 1 - network failure

To recreate this one, just turn off your network connection and start a flow. The job will fail trying to pull the docker image. However, in this case we do get some visibility in the sessions page:

Question 1: Is that sufficient for this case? Or do we want more information here, rather than "Session failed"?

Example 2 - DWS configuration error

To recreate this one, I apply this patch to my AI Gateway: patch.txt

Then I run a fix_pipeline_next flow. This is the output I see in sessions:

There is an error on the DWS side here. So we are correctly showing the Status as failed but we dont show "Session failed" like in the other case.

Question 2: Can we add "Session Failed" to the session feed on the frontend in this case? The status is set to failed so we have that data, I'm just wondering if we can add to the feed as well.

Question 3: Similar to the first example, do we want more information here about how the failure happened?

Please let me know if I'm on the wrong track here. Trying to come up with some reproducible examples to work with.