We'll test a fix that ignores the result of publish(event) and goes on to the next pickup hub. If the user goes to the failed pickup hub won't see his input as long as the connection is failing. As before he could reenter his input causing some distortion with "double" events. As soon as the connection stays, the state of the pickup hub is updated in the UI.
A better behavior would be to show the user input immediately in the UI, but this requires more development effort. We'll experiment with this fix so far to see, whether the drivers can work better or not.
We'll test a fix that ignores the result of publish(event) and goes on to the next pickup hub. If the user goes to the failed pickup hub won't see his input as long as the connection is failing. As before he could reenter his input causing some distortion with "double" events. As soon as the connection stays, the state of the pickup hub is updated in the UI.
A better behavior would be to show the user input immediately in the UI, but this requires more development effort. We'll experiment with this fix so far to see, whether the drivers can work better or not.