Add afterCommit hooks for globals, fields, and collections

[6TELOIV]

Currently, there is no way to fire off some code immediately after data is committed to the database. This missing feature is useful for tasks where it's important that the APIs are returning the new data and not the old. Examples:

• To send a slack message or create a social media post with a link that depends on an updated og:image/og:description
• To invalidate a CDN that will immediately pro-actively re-fetch the data.
• To log analytcs without delaying the save.

The Job Queue serves a similar function, but it doesn't have a way to fire off the delayed action immediately after the transation is complete, and if the transaction fails from a later hook, the job can't know this.

[AlessioGr]

I agree such a hook would be useful. In the meantime, you could use the job queue for this.

In your afterChange hook, you can call payload.jobs.queue({ req }). Make sure it's on the same req. That way, the job won't be queued until the transaction is committed, as it will be part of the same transaction.

but it doesn't have a way to fire off the delayed action immediately after the transaction is complete

That's true - using this workaround, you'll have to rely on the speed of your job queue autoRun configuration.

and if the transaction fails from a later hook, the job can't know this.

Using this workaround, if the transaction fails, the job won't be added to the queue as the job document creation will be rolled back.

[6TELOIV]

That's a good point; I didn't realize the jobs queue local API used the transaction.

I also was able to work around this by manually committing the req.transactionId if present, which is certainly more dangerous than the job option, but has the benefit of being quicker.

Not sure yet which way I'll go for now, but definitely having a hook for this (I think afterCommit is an understandable name) would be very nice.

[andershermansen]

Can nextjs after function be used for this? 🤔
https://nextjs.org/docs/app/api-reference/functions/after

[6TELOIV]

This works, but I'm only confident if the change happened in a REST API request; the Local API timing could be different, I suspect.

[6TELOIV]

Additionally, after has implementation overhead for severless platforms that may or may not be available for all users.

https://nextjs.org/docs/app/api-reference/functions/after#platform-support
https://vercel.com/docs/functions/functions-api-reference/vercel-functions-package#waituntil

[6TELOIV]

I think for consitency and interoperability with non-transaction situations, the afterCommit hooks would run after all afterChange and afterOperation hooks, and after the transaction is committed (if any). I'm not sure the use case in knowing whether or not a transaction was used, but perhaps the transacitonId can remain on the req, or it can be renamed to committedTransactionId for this hook (for clarity that it's no longer good to use, and also to ensure that it's not accidentally passed to the local API)