# Fix for jobs left in progress after lost GitHub events

Source: https://sengi.run/changelog/2026-11-17-fix-for-jobs-left-in-progress-after-lost-github-events

By Sengi · Published Nov 17, 2026

## What changed?

Some jobs on Sengi runners could stay marked in progress, and go unbilled, when GitHub's job event arrived out of step or was lost during a network interruption. Both cases are now handled.

## Details

GitHub sometimes sends a job event whose status does not match its action, for example a completed event with the job still listed as in progress. Sengi used to refuse these, so the job stayed in progress. It now accepts them and records the job as completed.

Failed deliveries from GitHub used to be retried only once. They are now retried on every scan until one succeeds, except deliveries Sengi deliberately refused, which GitHub is no longer asked to resend. If a runner was removed before its job's completion event arrived, Sengi now reads the job's final status from GitHub and records its minutes. If a job you ran still shows as in progress after it finished, contact support.

## Related pages

- [Troubleshooting](https://sengi.run/docs/troubleshooting)
- [Billing and free minutes](https://sengi.run/docs/billing)

## More changes

- Next: [Fix for jobs stuck after a deleted repo's name is reused](https://sengi.run/changelog/2026-11-17-fix-for-jobs-stuck-after-a-deleted-repos-name-is-reused) (Nov 17, 2026)
- Previous: [Email when your free minutes for the month run out](https://sengi.run/changelog/2026-11-17-email-when-your-free-minutes-for-the-month-run-out) (Nov 17, 2026)
- [All changes in the Sengi changelog](https://sengi.run/changelog)
