ash_oban discarded jobs with `trigger_no_longer_applies`
I'm using ash_oban, and I keep seeing quite a few jobs getting discarded with
I've started observing some very strange timing bugs recently (the details of which I won't go into here) which are making me suspect these errors could be indicative of something wrong on a deeper level. I'm hoping to at least get a feel for how to interpret these errors, which I can then use to go debug the setup I have.
** (Oban.PerformError) MyApp.SomeDomain.SomeResource.AshOban.Worker.SomeTrigger failed with {:discard, :trigger_no_longer_applies}I've started observing some very strange timing bugs recently (the details of which I won't go into here) which are making me suspect these errors could be indicative of something wrong on a deeper level. I'm hoping to at least get a feel for how to interpret these errors, which I can then use to go debug the setup I have.
Solution
It happens if jobs are completed in between the scheduler running it's read query and scheduling the jobs.
https://hexdocs.pm/ash_oban/dsl-ashoban.html#oban-triggers-trigger-trigger_once?
and when the second job runs the read action doesn't return the record anymore because the previous job already set the state to something else, which makes the where condition not apply anymore. If that happens the job is discarded
https://hexdocs.pm/ash_oban/dsl-ashoban.html#oban-triggers-trigger-trigger_once?
and when the second job runs the read action doesn't return the record anymore because the previous job already set the state to something else, which makes the where condition not apply anymore. If that happens the job is discarded
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Was this page helpful?
