I am noticing a delay when direction and location information from my device changes and the updated values are used during a Camunda workflow. I sometimes use an online compass, which is a browser-based tool that uses the device’s GPS location and sensors to show the current direction and orientation. It helps check movement direction and understand how the device detects position changes.
The problem is that when I move the device or change direction, the compass value updates immediately on the device, but the related information used in the workflow does not always seem to match the latest value. In some cases, an older direction or location value appears to be processed even though the device has already provided a new update.
For example, when walking with a phone and changing direction several times, the online compass can show the new direction quickly. However, when the same type of changing data is involved in a Camunda process, I notice that the workflow may continue with previous information for a while. I am not sure if this happens because of event timing, message handling, or the way process instances receive updated data.
Has anyone experienced similar behavior when handling frequently changing values in Camunda? How do you usually manage situations where external data can change multiple times during an active workflow? I am especially interested in how to prevent older values from being used when a newer update is already available.
I would also like to know if there are specific Camunda settings or workflow patterns that can help with real-time updates from devices. For example, is it better to send each location change as a separate event, or should the workflow wait for a certain condition before continuing? I would appreciate any advice from people who have dealt with sensor data, GPS updates, or other changing external information in Camunda processes.