Client Tracking Id for built in triggers in logic app standard

Sumit Gaur 235

Hi,

i have seen that for lots of build in connectors we don't have a support for adding a custom client tracking id on the trigger e.g., when a blob is received.

there is indeed a tracking id option like you get on actions but it doesn't seem to work an capture the id and sometime causes the trigger to not work.

we do have this option in service bus and http trigger but i could lot of other adapter missing this .e.g. Blob trigger, SFTP trigger.

is there a way we can add a custom client tracking id from the metadata received in trigger, is it possible that is not supported through the UI but is supported on the workflow code level?

VenkateshDodda-MSFT 20,696 Reputation points Microsoft Employee

2024-03-04T09:45:52.03+00:00

@Sumit Gaur Thanks for reaching out to Microsoft Q&A, apologies for any inconvenience caused on this.

I am checking with the internal team on this and will update you here Once I hear back from them.
Sumit Gaur 235 Reputation points

2024-03-26T14:56:15.83+00:00

@VenkateshDodda-MSFT any update you got from the internal team?
VenkateshDodda-MSFT 20,696 Reputation points Microsoft Employee

2024-03-28T04:54:16.3833333+00:00

Hello @Sumit Gaur ,

Following up to see if you have a chance to check my previous response and helped. Do let us know if you have any further questions on this.

1 answer

VenkateshDodda-MSFT 20,696 Reputation points Microsoft Employee

2024-03-27T01:27:32.69+00:00
@Sumit Gaur Thanks for your follow-up on this. apologize for the delay in response.

Our internal team has confirmed that adding client tracking id from UI is not supported for all the connectors.

Alternatively, you can the below code block in code view under the trigger in your workflow in order to get the tracking id.

"correlation": { "clientTrackingId": "<tracking id>" },

Hope this helps, let me know if you have any further questions on this.
Please sign in to rate this answer.
Sumit Gaur 235 Reputation points

2024-03-29T13:36:58.3166667+00:00

@VenkateshDodda-MSFT i will try this and let you know if this works or throw any error.

VenkateshDodda-MSFT 20,696 Reputation points Microsoft Employee

2024-04-01T04:10:10.78+00:00

Sumit Gaur Thanks for your response will wait for further updates from you.

Sumit Gaur 235 Reputation points

2024-04-01T14:16:22.9366667+00:00

@VenkateshDodda-MSFT i have tried it both in VS Code and portal and it don't work, adding it workflow.json make the workflow don't show up in VS Code when you run the debugger while on portal it does save the workflow but trigger stops working.

below is what is used to fetch blobname minus the subfolders in a container.

"correlation": { "clientTrackingId": "@{triggerBody()?['properties']['blobName']}" }

VenkateshDodda-MSFT 20,696 Reputation points Microsoft Employee

2024-04-02T09:45:48.75+00:00

Sumit Gaur Thanks for your response Let me check and get back to you on this. Mean while could you please share the complete workflow.json file(Excluding PI information) to check and assist you further.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Client Tracking Id for built in triggers in logic app standard

1 answer

Your answer