I'm testing that my application adds jobs to quantum correctly based on some business restrictions and I'm using on_exit to remove jobs again after tests. This however is causing issues with the ecto sandbox, because even after calling Scheduler.delete_job the job has not been removed and jobs access the db even after being supposed to be removed. Currently I need to add a timeout here to delay my on_exit callback. While working on said feature I had similar issues with run_job, which also is async.
It would be great if the async nature of those job APIs would be highlighted in the docs and I'd really like to see options to have those operations be done synchronous as well.
I'm testing that my application adds jobs to quantum correctly based on some business restrictions and I'm using
on_exitto remove jobs again after tests. This however is causing issues with the ecto sandbox, because even after callingScheduler.delete_jobthe job has not been removed and jobs access the db even after being supposed to be removed. Currently I need to add a timeout here to delay myon_exitcallback. While working on said feature I had similar issues withrun_job, which also is async.It would be great if the async nature of those job APIs would be highlighted in the docs and I'd really like to see options to have those operations be done synchronous as well.