Based on https://redhat-internal.slack.com/archives/C059YMMB664/p1738136229211769?thread_ts=1737962355.145659&cid=C059YMMB664 and following discussion:

The goal is in listing all workflows to the user along showing their Available/Unavailable statuses. The status is a hint for the user about eventual issues during the workflow execution.

The backend will repeatedly maintain cache based on workflow pods' statuses and provide synchronous endpoint to force-check a selected workflow pod status.

The frontend will show a new column in the list along info what it means. And does checks to decrease probability of user typing in parameters but not being able to run it.

Additional details in the slack thread linked above.