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
If in the mongo database there are any pending messages when the module is starting, in the start() method there is a check to load and send those messages:
if (persistorAddress != null) {
loadMessages();
}
But at this moment, there isn't any registered processor that can handle the delivery of the loaded messages. So those messages are never processed.
I think that the best place to check if there is any pending message is in the handler when registering a processor for a first time or maybe add a new address to be called when the module is deployed and the processors are configured (maybe "<module_address>.pending" )
The text was updated successfully, but these errors were encountered:
If in the mongo database there are any pending messages when the module is starting, in the start() method there is a check to load and send those messages:
if (persistorAddress != null) {
loadMessages();
}
But at this moment, there isn't any registered processor that can handle the delivery of the loaded messages. So those messages are never processed.
I think that the best place to check if there is any pending message is in the handler when registering a processor for a first time or maybe add a new address to be called when the module is deployed and the processors are configured (maybe "<module_address>.pending" )
The text was updated successfully, but these errors were encountered: