Messaging Event

RE: Messaging Event

Stefan Helzle — Tue, 25 Jul 2023 09:10:27 GMT

Messaging is special ....

RE: Messaging Event

Saahil Mulla — Tue, 25 Jul 2023 08:57:08 GMT

Ok, got it, any how it doesn't come up in the monitoring state as failed Process, but we get an email about the error. Thank you 🙂

RE: Messaging Event

Stefan Helzle — Tue, 25 Jul 2023 08:38:30 GMT

I see. And this is exactly what will fail. Accessing a non-existing field in a message using dot-notation creates the error messages you see.

RE: Messaging Event

Saahil Mulla — Tue, 25 Jul 2023 07:38:03 GMT

Each listener is looking for a different property using dot notation. For specific tasks we are sending specific property via a send message event. If the property exist we are storing in pv! and using it in this listener process model.

At a time the message will hold specific property.

RE: Messaging Event

Stefan Helzle — Tue, 25 Jul 2023 07:24:08 GMT

I think that the issue is, that this message is consumed by all your listeners. In case a listener tries to access an attribute like "rejectToRequestor", it will create this error message you get.

Do you use dot-notation or index()/property() to fetch values from these messages? Dot-notation will fail if the property does not exist.

And, in case you want the process to stop after consuming the first message, I suggest to configure the end events to terminate the process.