It happens every minute (which is the default interval?), so has been persistent since we deployed 1.5.
On the whole our database load is now a fraction of what it was, so we’re so, so grateful, thank you for continuing to improve this library 
We have a few odd issues that we’re trying to narrow down. One is what Adam mentioned above. It’s not critical, but is an error we’re getting and we’re not sure why. We have a very vanilla configuration, we’re not passing any options.
We are using some regular Oban.Worker and some Oban.Pro.Worker. Does it play nicely with regular Oban.Worker? Should we convert all Oban.Worker to Oban.Pro.Worker?
Another more critical issue is that jobs that are part of some chains or workflows are having their scheduled_at set to 3000-01-01 00:00:00 sometimes. I’ve been trying to narrow down if it’s something we’re doing but I don’t think it is? Here’s one snippet:
def workflow(listener, meeting, opts) do
jobs = jobs(listener, meeting, opts)
deps = Enum.map(jobs, &"action_#{&1.changes.args.action_id}")
start =
Workflow.new()
|> Workflow.add(
"extract_facts",
ExtractFacts.new(%{meeting_id: meeting.id})
)
jobs
|> Enum.reduce(
start,
fn %{changes: %{args: %{action_id: id}}} = job, acc ->
Workflow.add(acc, "action_#{id}", job)
end
)
|> Workflow.add(
"run_analytics",
RunAnalytics.new(%{meeting_id: meeting.id})
)
|> Workflow.add(
:done,
AllAutomationsDone.new(%{meeting_id: meeting.id}),
deps: ["run_analytics" | deps]
)
end
For some reason the AllAutomationsDone job gets a scheduled_at of 3000-01-01 00:00:00. I’m not sure if that’s a placeholder value of some sort, but it never recovers, and it’s just stuck there AFAICT.
We also have other jobs that are not part of workflows, but do pass the chain option, such as:
use Oban.Pro.Worker,
queue: :sync,
max_attempts: 2,
chain: [by: [:worker, args: :integration_id]]
One last oddity is that all our discarded jobs have disappeared, we are permanently at zero jobs in discarded (which is strange always a few known failures happening). They seem to be getting pruned immediately. Still trying to narrow down what’s going on there, but it is definitely new as of the 1.5 release (where I only made the mechanical changes from the Oban Pro 1.5 upgrade docs, which were very helpful).
Also, is this the best place to report these kinds of issues? Happy to move this elsewhere if needed.
. It’s mapping the result of a 
