Re: [D] [GitHub] Workflow runs with in_progress status are skipped and not collected after completion [devlake]

["NhanDuong21 (via GitHub)" <gi...@apache.org>]

GitHub user NhanDuong21 added a comment to the discussion: [GitHub] Workflow runs with in_progress status are skipped and not collected after completion

There is now an upstream fix for this, newer than the replies above: [#9162](https://github.com/apache/devlake/pull/9162) was merged on September 24 and is included in [v1.0.3-beta18](https://github.com/apache/devlake/releases/tag/v1.0.3-beta18).

The collector now stores unfinished runs and revisits the oldest unfinished run when choosing the next incremental collection window. That lookback is bounded to 14 days, so your 3–4-hour workflows fall within it. This does not require a custom image.

I would back up the database, test the beta18 release images in a staging copy of your ECS deployment, and check one known run through both `in_progress` and `completed` using your existing two-hour incremental schedule. The release's Compose attachment lists the matching backend, Config UI and dashboard image tags.

One important distinction: runs discarded by v1.0.2 are not automatically recovered by the new unfinished-run tracking. The fix documents a one-time backfill with `TimeAfter` covering their creation dates. Since your previous full refresh removed dashboard history, do not repeat a one-month refresh on production without a backup and a staging test covering the full history you intend to retain. Data that GitHub no longer exposes may require restoring your earlier backup.

GitHub link: https://github.com/apache/devlake/discussions/9125#discussioncomment-18720878

----
This is an automatically sent email for dev@devlake.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@devlake.apache.org