GitHub user tomm1990 added a comment to the discussion: [GitHub] Workflow runs with in_progress status are skipped and not collected after completion
@vasukiiyengar98 short answer: no official release or config I can find that keeps `in_progress` runs and updates them when they complete. Full/backfill sync is still the supported workaround on stock images. I checked beyond v1.0.2: - `v1.0.3` / `v1.0.4-alpha`: same completed-only filter + `Skipping run ... with status ...` path as 1.0.2 - `main` / recent `v1.0.3-beta*`: collector was rewritten for the `/actions/runs` pagination caps ([#8844](https://github.com/apache/devlake/pull/8844) / [#8842](https://github.com/apache/devlake/issues/8842)), but it still only keeps `status == "completed"` (comment in code: “only keep completed runs”). No in_progress persist + refresh So upgrading the official image can help large-repo collection reliability. It does not change the long-running Actions miss you hit. I also could not find an existing issue/PR specifically for “store in_progress GitHub Actions runs and update on completion.” Closest related work is the pagination fix above, which is a different problem. If you need that behavior, filing a new GitHub issue against `apache/devlake` (plugin=GitHub, your ECS image tag, skip log lines, and one run id that never lands after incremental) is the right next step for an official fix. Until then: stay on official images, keep incremental for day-to-day, and schedule full sync / a `timeAfter` window that covers those runs’ `created_at` after long workflows finish. GitHub link: https://github.com/apache/devlake/discussions/9125#discussioncomment-18364053 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
