We are currently performing maintenance on Appian Community. As a result, discussions posts and replies are temporarily unavailable. We appreciate your patience.
I have few active receive message(cancel_process) event with a condition to match a request id and then proceed. A different process executes and send message(cancel_request) with request id to all receivers, this call does not have destination process ids. After this, all active receive message node moved further even though the condition was false.
The receive message executes even when the condition evaluated to false, has anyone faced this issue?
Thanks in advance!
Discussion posts and replies are publicly visible
I only see this behavior in case the condition runs into an edge case. Can you share that code snippet and event configuration?
Send and receive message configuration snapshot attached.
We are sending an ID from send message and same is validated in receive message. I confirm we have value for pv in send and receive process.
Seems to be OK on the first sight. Is there a specific reason to broadcast that message instead of targeting a specific instance? I assume you are aware of the best practices around messaging.
These are old processes, still working this way. We are gradually simplifying these, yes I agree we should target a specific process or minimize the use of this event but this sudden behavior has made many of our instances terminate abruptly.
Also, we modified and deployed the process model which contains send message, could it be somewhere related to this issue?
I understand. Debugging messaging issues is really tricky as there is no information recorded.
But I saw situations in which a condition was ignored when the message did not contain that specific value.
Yeah looks like this is what might have happened. As there was no specific reason for this, we will work towards removing this event.
Thanks for your input Stefan! Appreciate it!