Currently, Harness displays queued executions with a "Running" status. This is misleading - developers have to drill into the execution steps to discover their pipeline is actually queued, not running.

Please label queued executions as "Queued" to match the actual state.

Why it matters: This creates unnecessary confusion and wastes developer time. Standard platforms like Jenkins handle this correctly by showing "Queued" status upfront.

This is a simple UX fix that would eliminate a daily friction point for our team.