How to avoid unwanted flow triggers for Outlook trigger "When an event is added, updated or deleted (V3)"

[dragondive]

I set up an automation flow on the Outlook trigger "When an event is added, updated or deleted (V3)". Within the flow, I check for the ActionType. Based on whether it is "Added" or "Updated", I perform certain tasks. However, I noticed that the flow triggers randomly without any explicit event update by the user.

I compared the outputs of the trigger in the two cases: (1) when there is a "real" update by the user and (2) when the update is "unwanted". 

 It looks like the "unwanted" update was triggered due to a change in the event's internal metadata (Location, Set-Cookie, x-ms-request-id). There are no other changes in the event's body (except the "lastModifiedDateTime", which is quite obviously due to this "unwanted" internal update)

I don't know what these fields are, or what causes them to get updated, but I want to avoid the flow getting triggered for these updates. Since the number of flow triggers also counts against my usage limits, I don't want any of Microsoft's internal updates to use it up. 

I thought to update the trigger's Trigger Conditions from the settings, but I don't know how I can specify there that "do not trigger this event in case of updates only to the event headers". The only workaround I have is to explicitly check if the event's subject, start time, end time, location, description (meeting body), etc. have changed, and ignore the trigger when these are not changed. But this still counts as a trigger against the usage limits. 

The official documentation here Office 365 Outlook - Connectors | Microsoft Learn mentions:

Trigger provides unnecessary updates

When an event is added, updated or deleted (V3)

An event can be updated due to internal Exchange processes and the trigger will fire again because of that. Users can filter a trigger's outputs on the Action Type parameter to ignore unnecessary updates.

But it is not clear how to use the Action Type parameter as suggested because in both the cases, the Action Type is the same ("Updated").

Are there any known solutions or ideas to solve this problem?