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

Roman Eisner
2026-04-15T16:10:51Z

Eventually duoMessages will render empty after 30 days, so it will be hard to determine what the failure was when displaying the message

I think one approach that might work here is to add a new field for workflows called summary that contains some text describing what happened in this workflow. We already have status which describes whether it succeeded or failed, but the summary field could contain:

If the flow fails before running on the AI Gateway side, it could contain whatever failed on the rails side (e.g. network failure)

If the flow fails somewhere in DWS, we could have DWS update the workflow summary with what failed there

If the flow succeeded, we could have the LLM summarize the flow in a single sentence. Something like "The pipeline was fixed and an MR was created"

In the second case, we could move some of the error handling to the LLM as well. Have it summarize why it failed, but that could be an iterative thing.

This approach has the advantage of having some intuitive notion of what failed, but as you mentioned, it could also stick around longer as it doesnt take up as much space as the checkpoints. WDYT?

CC @bastirehm