Keeping Oban's time units explicit

almirsarajcic

47 minutes ago

0 comments

Copy link

AppSignal Slow Ecto Query? See The Exact Line. Trace Ecto queries to the line of code. Errors, traces, logs, BEAM metrics in one tool. Start Free, No Card Start Free, No Card

Oban’s Lifeline and Pruner accept raw integers in different units: rescue_after is milliseconds, while max_age is seconds.

On current Oban releases, use period tuples so the unit stays with the value:

config :my_app, Oban,
  lifeline: [rescue_after: {2, :hours}],
  pruner: [max_age: {7, :days}]

Reusing :timer.hours(168) for max_age would keep jobs for 604,800,000 seconds, or about 19 years, instead of seven days.

Older Oban releases used Oban.Plugins.Lifeline and Oban.Plugins.Pruner and accepted integers only, so check the documentation for the version you run.

https://oban.hexdocs.pm/Oban.html

Keeping Oban's time units explicit

Comments (0)