OpenFn / OpenFn/lightning

Update oban_pruner.ex policy

Open
#2,835 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Current Policy: In Oban, successful jobs are cleared from the DB every 10 minutes, and discarded jobs stay FOREVER so that they can be analyzed daily, retried manually, or deleted because we know why they failed and they don’t need to be re-run.
Oban failures in V2 are still being kept to be analyzed (currently by @taylordowns2000 on a weekly basis).

Solution: Update oban_pruner.ex policy to purge failed/discarded jobs after 4 weeks. Additionally on our Sentry response protocol, adding the analysis of the issues every 4th week of the month.

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.

Research direction

Start by reading oban_pruner.ex and trace the existing retention policy for successful and discarded jobs. Update the policy so failed or discarded jobs are purged after four weeks, and identify where the Sentry response protocol documents its recurring analysis. Done means both the retention behavior and the fourth-week analysis requirement are represented.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.