I am currently using Events v2 to send incident ‘triggers’ to the API. In that POST there is a custom dedup_key that I am sending. That dedup_key seems to be showing correctly both in the 200 response and when I view the message in the web administration site. However when I then send a ‘resolve’ event with the same dedup_key the incident is never acknowledged. I am formatting the resolve event according to documentation (https://v2.developer.pagerduty.com/docs/send-an-event-events-api-v2) and I receive a 202 in response but nothing happens.
Is this expected behavior with a custom dedup_key? Using the randomly generated one returned when I don’t specify one is possible but adds hassle/complexity because this code is running inside of a python lambda in AWS.