OpenFn / OpenFn/lightning

Recover stuck Oban jobs

Open
#4,708 0 comments 0 reactions 1 assignee View on GitHub

@midigofrank is already working on this.

Since May 6, 2026.

oban errors
Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

When the lightning instance that was executing an oban job is killed abruptly, say OOMKill, the job will get stuck in executing state.

This issue allows lightning to recover these stuck jobs. For now, we only know of data_retention jobs.

Oban has a plugin for doing this exactly, https://hexdocs.pm/oban/Oban.Plugins.Lifeline.html, but it has a bug disclaimer:

This plugin may transition jobs that are genuinely executing and cause duplicate execution. For more accurate rescuing or to rescue jobs that have exhausted retry attempts see the DynamicLifeline plugin in Oban Pro

https://hexdocs.pm/oban/ready_for_production.html#rescuing-jobs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.