Clarity Needed on Logic Apps Trigger and Run History

Question

Clarity Needed on Logic Apps Trigger and Run History

cloudteam 60

What is the relationship between the trigger history identifier and the run history identifier in Logic Apps (standard/consumption)?

Will the trigger history identifier and run history identifier always be the same?
When a trigger fails (any failure statuses), will there be a corresponding run history record?
For a single trigger execution, can there be multiple run history records?

An update on these questions would be appreciated.

Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T14:03:28.72+00:00
@cloudteam ,

The relationship between the trigger history identifier and the run history identifier in Azure Logic Apps is as follows:

The trigger history identifier and run history identifier are not always the same. Each time a trigger successfully fires, Azure Logic Apps creates a unique workflow instance, which is represented by a run history record. The trigger history records all attempts, while the run history records instances of workflows that were executed.

When a trigger fails (any failure statuses), there may not be a corresponding run history record. If a trigger fails, it may not create a workflow instance, meaning no run history record will be generated for that trigger attempt.

For a single trigger execution, there can be multiple run history records if the trigger fires multiple times successfully. Each successful trigger execution results in a separate run history record, particularly if the trigger is designed to handle multiple events or items simultaneously.

ref:https://learn.microsoft.com/en-us/azure/logic-apps/view-workflow-status-run-history?tabs=consumption#review-trigger-history
cloudteam 60 Reputation points

2025-04-30T09:47:59.7466667+00:00
Hi,

From @Khadeer Ali

The trigger history identifier and run history identifier are not always the same.

From @RithwikBojja

No, Sometimes, When the trigger is fired and is true then the run id will be same. But it will definitely not be same If Fired is false i.e triggers fail and instance will also be not created for them.

I am looking for a clarification on when the trigger identifier and run identifier wouldnt be same.

If possible, could you please provide an example scenario where they differ? Additionally, a simple procedure to replicate such a situation would be very helpful for better understanding.

Thank you for your support!
RithwikBojja 2,080 Reputation points Microsoft External Staff

2025-04-30T15:05:43.2533333+00:00

Hi @cloudteam ,They are typically the same. But there are edge cases where this could be different. If a Logic App is retried or re-executed due to a failure or manual resubmission, the Run History ID could change, but the Trigger History ID will remain the same because the trigger event hasn't changed. If multiple Logic Apps are triggered by the same event, they will share the same Trigger History ID but have different Run History IDs.

1 answer

Your answer

Khadeer Ali 4,960 Reputation points Microsoft External Staff

2025-04-29T14:03:28.72+00:00

@cloudteam ,

The relationship between the trigger history identifier and the run history identifier in Azure Logic Apps is as follows:

The trigger history identifier and run history identifier are not always the same. Each time a trigger successfully fires, Azure Logic Apps creates a unique workflow instance, which is represented by a run history record. The trigger history records all attempts, while the run history records instances of workflows that were executed.

When a trigger fails (any failure statuses), there may not be a corresponding run history record. If a trigger fails, it may not create a workflow instance, meaning no run history record will be generated for that trigger attempt.

For a single trigger execution, there can be multiple run history records if the trigger fires multiple times successfully. Each successful trigger execution results in a separate run history record, particularly if the trigger is designed to handle multiple events or items simultaneously.

ref:https://learn.microsoft.com/en-us/azure/logic-apps/view-workflow-status-run-history?tabs=consumption#review-trigger-history
cloudteam 60 Reputation points

2025-04-30T09:47:59.7466667+00:00

Hi,

From @Khadeer Ali

The trigger history identifier and run history identifier are not always the same.

From @RithwikBojja

No, Sometimes, When the trigger is fired and is true then the run id will be same. But it will definitely not be same If Fired is false i.e triggers fail and instance will also be not created for them.

I am looking for a clarification on when the trigger identifier and run identifier wouldnt be same.

If possible, could you please provide an example scenario where they differ? Additionally, a simple procedure to replicate such a situation would be very helpful for better understanding.

Thank you for your support!
RithwikBojja 2,080 Reputation points Microsoft External Staff

2025-04-30T15:05:43.2533333+00:00

Hi @cloudteam ,They are typically the same. But there are edge cases where this could be different. If a Logic App is retried or re-executed due to a failure or manual resubmission, the Run History ID could change, but the Trigger History ID will remain the same because the trigger event hasn't changed. If multiple Logic Apps are triggered by the same event, they will share the same Trigger History ID but have different Run History IDs.

Answer 1

Hi @cloudteam ,

Will the trigger history identifier and run history identifier always be the same?

No, Sometimes, When the trigger is fired and is true then the run id will be same. But it will definitely not be same If Fired is false i.e triggers fail and instance will also be not created for them.

When a trigger fails (any failure statuses), will there be a corresponding run history record?

If Trigger fails, there will be no run history loaded as the trigger only failed and the logic app does not create a new instance to it.

For a single trigger execution, can there be multiple run history records?

Every time a trigger fires successfully, Azure Logic Apps creates a separate workflow instance and executes it. By default, these instances run in parallel, allowing each workflow to start immediately without waiting. If multiple events or items trigger the workflow simultaneously, you'll see a separate trigger entry for each one with the same timestamp.

Trigger History means, the number of times the trigger is checked. It is not if the workflow called or not. It checks if the trigger condition is met or not.

If you are using http manual trigger, then whenever it is called it will show in trigger history, that the workflow is successfully called:

enter image description here

It does not show the entire flow.

It also contains the history of connection establishment if you are using any other service connector as below:

enter image description here

So it just gives us information about the first action of workflow i.e the trigger.

Run History contains the instances created. If the trigger is fired correctly, then it creates the instance and the workflow starts executing, here you can check the history or result of each flow if it succeeded, failed or skipped.

If this answer was helpful, please click "Accept the answer" and mark Yes, as this can help other community members.

enter image description here

If you have any other questions or are still experiencing issues, feel free to ask in the "comments" section, and I'd be happy to help.

RithwikBojja 2,080 Reputation points Microsoft External Staff

2025-05-02T03:03:27.3466667+00:00

Hi @cloudteam ,They are typically the same. But there are edge cases where this could be different. If a Logic App is retried or re-executed due to a failure or manual resubmission, the Run History ID could change, but the Trigger History ID will remain the same because the trigger event hasn't changed. If multiple Logic Apps are triggered by the same event, they will share the same Trigger History ID but have different Run History IDs and I wanted to follow up and see if the given answer was helpful. If this resolves your issue, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.

Share via

Clarity Needed on Logic Apps Trigger and Run History

1 answer

Your answer