Share
ReportHey all, I have a custom connector.When my users use it in flow they can add the actions multiple number of times in a flow. Now my action is connected to backend where a database entry will be made for it when flow runs. Basically, we need to recognize an action of the connector(a guid or something) that remains fixed for that instance of the connector throughout that flow life cycle(EACH RUN). It should not change. Now when we delete it and add it again, the guid should change as technically we have added a new instance.
What we have tried:
1)guid() expression: changes on every run
2)Dynamically bringing a guid generated from backend: was working fine, when the instance was created, a guid came from my backend and when the action ran, the guid was sent in request body and recorded at backend. It remained same throught every run of the flow. We got a different guid when another instance of the connector was added too.
BUT this stopped working recently because every time we add a new instance, it has the same guid as other instances, as if the first request to get guid is getting cached and being reused. It only changes if one makes new connection for new instance but that is not feasible for our users.
3) workflow() gives details of flow, so not an option
So, how to identify the instances of one connector in one flow?
All responses (
Answers (
497
