Bump this up for better pagination, giving the user the ability to have 10, 25, 50 or 100 workflows per page would be terrific.

Slightly confused... Running workflows should always be sorted to the top if sorting by "Latest Crawl".

EDIT: Nope! They aren't.

Noted on the page list scrolling. Thanks for feedback. Some thoughts on how to solve that are available in #747

We may want to support additional sorting by workflow state ordered as running states -> waiting states -> failed -> success -> never, since "Latest Crawl" doesn't address the case when a crawl starts while there's another workflow still running. And/or a state filter on workflows.

We'll look into general pagination improvements in #1944

For now for the backend change to make is to ensure that running crawls are always floated to the top for "Latest Crawl" sort order.

We may look into additional changes to make but want to avoid having an opaque "Last Updated" type sort option with a complicated algorithm, as we had that before and removed it because users didn't understand the logic.

Got started on this in #2528 — this'll add an option to show running crawls separately from the rest of the crawls, so far with a separate pagination if necessary for both groups. Once this is done I'll also work on getting pagination persisted in URLs (e.g. /orgs/emmas-local-org/workflows?page=14)!

Another option is to reuse the super admin interface we already have for all running crawls, and just make it available for a single org.