[Bug] Report status desyncs from query state — stuck "Running" with no way to recover, cancel endpoint returns misleading 400

Summary

A report has remained in Running status for 125 hours even though both Trino queries are no longer active. One query is shown as failed, while the other remains incorrectly marked as queued.

Clicking the red cancel button sends the following request:

POST /report/rep_xxxx/cancel

The request returns:

400 Bad Request: No running query found

The report remains stuck and cannot be restarted.

Expected Behavior

GrowthBook should allow stale queued or running queries to be cancelled regardless of their age, clear the report’s running state and allow the report to be restarted.

Current Behavior

1. The report header displays Running (125h).
2. The query details show one failed query and one query queued for five days.
3. The underlying queries are no longer running in Trino.
4. The cancel request returns 400: No running query found.
5. The report state does not change, preventing the customer from rerunning it.

Technical findings

The UI considers a report active when any query is marked as either queued or running. However, the report cancellation endpoint appears to search only for snapshots created within the last 24 hours that contain a query marked specifically as running.

This means an older report whose remaining query is marked as queued is displayed as running by the UI but cannot be found by the cancellation endpoint.

The cancellation lookup should include queued queries and should not prevent report-specific cancellation solely because the snapshot is older than 24 hours.