-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messages related issues (in dev.app) - 4 #1800
Comments
https://dev.app.spiff.status.im/i/3057 |
@madhurrya this might be another issue where the correlation name must not contain spaces. that might be something to try to make sure it acts the same way when there are no spaces. |
@burnettk tested it without adding a matching condition. In that case the receive data is empty. https://dev.app.spiff.status.im/i/3285 |
And if you take this one here it shows Receive data even before the message completes. May be I have not understood the concept there? |
maybe because of matching on empty correlations. we will take a look at this. |
Issue 1 is fixed. |
I think the new issue is slightly different and more interesting. The message receive task was started manually, not from a message start event, and was never given any correlation keys. This means its keys are empty and therefore it will receive any sender task for that same message. I've always wondered if it should act like this. The problem being that a message that was mistakenly never given any keys could hijack ongoing conversations between other process instances. |
Yeah the properties have been defined but it was never given any values to those properties prior to running. Which is why it's a blank dict on the receive. |
Do you mean a matching condition? |
FIXED 1. When a non admin user clicks on a message task, it gives this errorThe text was updated successfully, but these errors were encountered: