Logic Apps Standard - Service Bus In-App connector improvements for Peek-lock operations

WSilveira I have an additional question (We already have a running support ticket), but I was asked to check this blog.

We have been facing affinity issues, even though we followed the documentation, and got support and were pointed out to these new connectors.

For most of our integrations, the update of the connectors seem to work fine. However, when we use sessions for messages (between 2 logic apps in order to pick the right message based on a session id), it seems that we are forced back to the old connectors (messageid). These do not work with the new ones (locktoken). We also need to do changed in the code editor because the properties differ based on the selected approach. But the old connectors give us the affinity issue, which happen more than often.

So,

With this update we try to use this action:

But we are not able to complete the message with this action:

Which under the hood became  completeQueueMessageV2 operation (with lock-token). 

We get the error:

{
  "code": "ServiceProviderActionFailed",
  "message": "The service provider action failed with error code 'BadRequest' and error message 'It is not possible for an entity that requires sessions to create a non-sessionful message receiver. TrackingId:xxxxxxxxxxx_B0, SystemTracker:gi::G2:xxxxx:amqps://xxx.servicebus.windows.net/-xxxxxx;43:48:49:source(address:/sbq-xxx-in,filter:[]), bi::in-connection226763(G2-6416)::session226764::linkxxxxxxx, Timestamp:2024-08-15T13:59:33 TrackingId:xxxxxxxexxxxxxxx_G2, SystemTracker:gateway10, Timestamp:2024-08-15T13:59:33\r\nFor troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot.'."
}

This leaves a session based message on the queue, without any option to remove it. This seems to be a limitation with v2/preview actions. In my opninion the 

Any thoughts would be appreciated.