INN-2911: Fix empty event payloads in UI due to resolver bug #1258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The change introduced in #1238 changed how IDs are used (diff) within the
runner
service. This invalidated the previous fix in #1201.This issue happens as sometimes two different event ids are created for a single event which is another, separate issue. This is reproducible by using the Invoke or Sent event button via the UI, but doesn't happen when sending an event via curl. The fix in this PR makes this issue separate and not a problem.
Tested:
Motivation
This looks like there was a valid bug fix with #1201 then #1238 caused a regression due to a change in how IDs are handled.
Type of change (choose one)
Checklist
Check our Pull Request Guidelines