There’s something that makes me wonder: this async option probably makes sense only in after_commit callbacks, because it seems rare that you want to run something later even if there’s a rollback. So, the generic “Callback” name in the proposed job class is really not so generic in reality.
Taking that into account, I see this proposal as a too exceptional API to deserve being in core.
Of course, you could decorate after_commit in ApplicationRecord to do what you want if async is present and delegate to super.
--
Sent from Gmail Mobile