Skip to content

Oban Cron Integration: Consider attempts when reporting "failed" checkins? #963

Description

@Miradorn

Problem Statement

Hey!
We've been using the Oban Cron Integration and one of the problems we face is with "retries", e.g. when a worker fails, gets retried and succeeds in sentry we get a "failed" checkin and immediately after an "early" checking for the next time the worker is supposed to run.

Solution Brainstorm

I'm not sure what would be the best solution to this problem, e.g. simply just reporting when attempts are exhausted might have problems with timeouts or other "expectations"? Maybe some form of config to let the user decide the behaviour?

Metadata

Metadata

Assignees

No fields configured for issues without a type.

Projects

Status
Waiting for: Product Owner

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions