Skip to content

Use run_after_commit when triggering GraphQL subscription

What does this MR do and why?

Based on investigation done in #376699 (closed), triggering GraphQL subscription within a transaction can result to lock contention.

This prevents that by utilizing run_after_commit in after_transition hook of the state machine when triggering GraphQL subscription.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #376699 (closed)

Merge request reports

Loading