There are some edge cases related to real-time card updates for the Favorites Dashboard which require some SSE changes to adequately address:
- Pipeline and Multibranch Pipeline jobs will dispatch "job_started" events as soon as they are run, even if all executors are currently busy. This results in the favorite going into RUNNING status when the user would expect the job is really QUEUED. Tracked by
- Due to the above behavior, repeated runs of the same pipeline or MB pipeline lead to misleading behavior in the UI. The card will initially reflect the RUNNING state, but after the first job completes it will enter the SUCCESS or FAILED state and remain as such while other jobs are running. This is because no further events are received as the subsequent job runs are actually started.