:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
perf(signals): load findings summary candidate ids before the task run join (#119154)
posthog[bot]78acf2a18311
diff --git a/products/signals/backend/scout_harness/tools/runs.py b/products/signals/backend/scout_harness/tools/runs.pyindex 3a84570a4971..4b93a083cf98 100644--- a/products/signals/backend/scout_harness/tools/runs.py+++ b/products/signals/backend/scout_harness/tools/runs.py@@ -536,12 +536,14 @@ def fleet_findings_summary(*, team_id: int, window_hours: int = DEFAULT_FINDINGStouched_a_report = (~Q(emitted_report_ids=[]) & ~Q(emitted_report_ids__isnull=True)) | (~Q(edited_report_ids=[]) & ~Q(edited_report_ids__isnull=True))- candidate_ids = (+ # Load the ids first. As an `id__in` subquery, the planner can start from `posthog_task_run`,+ # which holds every product's task runs, instead of from these few scout runs.+ candidate_ids = list(SignalScoutRun.objects.filter(team_id=team_id, created_at__gte=window_start).exclude(metadata__has_key="scout_trial").filter(Q(emitted_count__gt=0) | touched_a_report).order_by("-created_at", "-id")- .values("id")[:FLEET_FINDINGS_SUMMARY_CANDIDATE_RUNS]+ .values_list("id", flat=True)[:FLEET_FINDINGS_SUMMARY_CANDIDATE_RUNS])# Order by completion (fall back to creation) so the cap keeps the *most recently emitted* runs,# matching the frontend's `completed_at ?? created_at` sort; `-id` tie-breaks on the time-ordered PK.