Enabling Service Bus and SAP built-in connectors for stateful Logic Apps in Standard

SumitGaur680 : The app setting is used solely for the affinity feature, it will not affect any other trigger/action/workflows. I suspect that there are other causes to why you see unusual behavior in the blob trigger/ peeklock history.

"if i remove this setting, then my logic app starts working only issue that i face is the workflow cannot complete/ dead letter the message. 

any suggestion how this can be fixed?": This is expected since the setting is needed to run stateful service bus with more than one worker/instance
"the error i see on app-insight is : The listener for function 'Functions.WorkflowDispatcher' was unable to start. An attempt was made to access a socket in a way forbidden by its access permissions.": I will need more information on this e.g. is this with the setting enabled or disabled, what is the scenario you are using?

Dhana1207 : I am unfamiliar with using logic apps standard on container instances and whether or not we are currently supporting this scenario. Let me reach out to some other members of the team to learn more about this and get back to you (please leave another message here if you do not hear back from me in a week).