Suspend behaviour

[frbk]

I am a bit confused about Argo UI when suspend: is utilized in a workflow. My goal is to add a job that I can manually execute, which will trigger the process of deploying new QA env, however, if suspend: is used, the pipeline gets stuck in a running state. It's a bit confusing because you have to look into it to make sure that build/test jobs are finished. Is this by design, or is there a plan to make it more clear?
Example of what I am talking about:

I am mostly comparing this feature to gitlab. It will pass the pipeline if build/test stages finish without issues: