Running tab is never unselected

[dragondgold]

When checking other job states like Discarded or Cancelled, the Running state keeps its "focus" state, making you think you are seeing jobs in Running, especially when the UI takes a couple of seconds to show the new state

Aside from fixing the "focus" issue, it would be nice to add a small loading indicator for when loading jobs of the newly clicked state takes a few seconds

[bgentry]

Ugh, yeah I've noticed this and keep meaning to try to fix it. I think it broke quietly with a dep upgrade long ago.

Aside from fixing the "focus" issue, it would be nice to add a small loading indicator for when loading jobs of the newly clicked state takes a few seconds

I think the reason for this is the 14M jobs in your table, that's a lot! Are you using the retention period settings of the job cleaner?

[dragondgold]

Ugh, yeah I've noticed this and keep meaning to try to fix it. I think it broke quietly with a dep upgrade long ago.

Aside from fixing the "focus" issue, it would be nice to add a small loading indicator for when loading jobs of the newly clicked state takes a few seconds

I think the reason for this is the 14M jobs in your table, that's a lot! Are you using the retention period settings of the job cleaner?

Yes, we use retention, it's 14 days now because it's useful for debugging issues. I don't know if it's a common usecase but maybe it's a good idea to move completed jobs to a different table after a few days so they can be around for longer without impacting performance? Similar to the dead-letter jobs mechanic.

[bgentry]

Fixed the UI issue in #526, thanks for reminding me about this!