-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
2.0.0
-
None
-
DevX 28, DevX 29
-
5
Symptom
Webhook events are not triggered on environments different than main, even if the definitions appear on Definitions App.
Cause
Sometimes on SaaS webapp (staging), after instance is restarted, this code:
environmentsClient
.getEnvironmentNames()
.forEach(environmentId -> EnvironmentContextPerThread.runInEnvironmentContext(environmentId, webhookDefinitionRegistry::onUpdate));
on Webhooks module startup, is only executed for main environment, but all environments are shown on Environment Switcher and Definitions app shows properly all webhook definition files by environment.
As other environments than main, are loaded asynchronously, when module starts up, definitions are not there and subscribers can not be created for webhooks. But later, those definitions are finally loaded, and appear properly on Definitions App (but subscribers still does not exist, because there were no events on webhooks telling that the definitions were loaded, so subscribers weren't created).
- relates to
-
MGNLHOOK-309 Make REST client environment aware on SaaS
-
- Closed
-
- mentioned in
-
Page Loading...
1.
|
Implement |
|
Completed | Milan Divilek | ||||||||
2.
|
Review |
|
Completed | Javier Benito | ||||||||
3.
|
piQA |
|
Completed | Javier Benito | ||||||||
4.
|
QA |
|
Completed | Oanh Thai Hoang |
|
