We have custom connectors in place to publish and subscribe to messages on Azure Service Bus. Camunda 8 is deployed on an Azure Kubernetes cluster. The connectors have worked fine for months in local environments. We’ve updated and published the connector in the cluster only to change the icon. It seems when I run a version of the process using the earlier version of the connector, correlation works fine on first attempt. When updating the model to use the current version of the connector, the correlation typically fails on first attempt of posting the message, but sending the same message again will correlate on the 2nd or 3rd attempt. Sometimes even then, the message is correlated on 2nd attempt, but the process doesn’t move ahead till the 3rd attempt when it correlates again and moves on.