This is somewhat related to [Link Removed] and was brought up by a [Link Removed]
Setting the CVar input.bRespectIMCPriortyForTriggers to false resolves the issue, but would re-introduce [Link Removed].
The additional "Add Mapping Context" call triggers a call to `IEnhancedInputSubsystemInterface::ReorderMappings`, which is where we are retaining the trigger state if needed, which is correct. The issue appears because the ActionInstanceData for that data is cleared though, so on the next tick it will re-evaluate the trigger state and fire the "triggered" event again.
[Image Removed]
[Image Removed]
Expected: You only see "Add" printed
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-361208 in the post.