You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you modify webhooks, the webhooks are re-registered. However, only the container that ran the original modification of webhooks is aware of this change. This causes the registered webhooks of the secondary instance to be out of sync, causing unexpected behavior when traffic is load balanced between the instances.
To Reproduce
Spin up two instances of Directus connected to the same DB & Redis server. Update webhooks on instance A, observer how the webhook doesn't fire when triggered from instance B.
Describe the Bug
When you modify webhooks, the webhooks are re-registered. However, only the container that ran the original modification of webhooks is aware of this change. This causes the registered webhooks of the secondary instance to be out of sync, causing unexpected behavior when traffic is load balanced between the instances.
To Reproduce
Spin up two instances of Directus connected to the same DB & Redis server. Update webhooks on instance A, observer how the webhook doesn't fire when triggered from instance B.
Errors Shown
n/a
What version of Directus are you using?
49d8975
What version of Node.js are you using?
16.15.0
What database are you using?
Postgres 13.5 w/ Redis 6.2.6
What browser are you using?
n/a
How are you deploying Directus?
Locally
The text was updated successfully, but these errors were encountered: