Imagine we hook a custom function to send an email (or another non-transactional BC operation) in the middle of a post function like C80 or C90 (without commits of course)...

The email has been sent and after that, posting fails rolling back all changes in Business Central tables... The user solves the problem in data and register again the document... the same email has been sent twice...

We need a standard infraestructure to schedule jobs like sending this emails 1 minute later for example... This way, the job is a record too in a BC table that will be rolled back if an error happens...

Now imagine this emails should attach a PDF from a BC report.... we should schedule first a JOB that generates the PDF and a second job that attach it and send the email, so second job execution is subrogated to first job execution success...

This standard "technology" could avoid locks when the concurrency is high if all standard and custom posting actions could be optionally scheduled automatically when locks happens...

Seems SAGE X3 do something like this for many user actions... I think BC should implement this out of the box.