# Why does an Event Hook send multiple requests **URL:** \ **Category:** Questions\ **Created:** [February 25, 2025, 2:50pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324 "2025-02-25T14:50:40Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![HennessyWorks](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@HennessyWorks](https://devforum.okta.com/u/HennessyWorks)\ **Post date:** [February 25, 2025, 2:50pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/1 "2025-02-25T14:50:40Z")
We use Event hooks with filtering to send various things into workflows and than do something, mainly around user gets added to one of these groups do X. We are running into an obnoxious issue where the event hook will fire two events that are exactly the same even down to the event ID. This isn’t a major issue but does cause impact some downstream services, as we have been able to build some logic into some flows where it does affect those services. But this leaves me thinking I might as well have just used a user added to group trigger and than done all the filtering in the flow, surely this isn’t the intended outcome of event hook filtering ? ---
**Author:** ![maxkatz](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/maxkatz/32/5624_2.png) [@maxkatz](https://devforum.okta.com/u/maxkatz)\ **Post date:** [February 25, 2025, 7:32pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/2 "2025-02-25T19:32:14Z")
Hi @HennessyWorks - Do you also see two events in the System Log? ---
**Author:** ![HennessyWorks](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@HennessyWorks](https://devforum.okta.com/u/HennessyWorks)\ **Post date:** [February 26, 2025, 8:37am UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/3 "2025-02-26T08:37:42Z")
Hey @maxkatz, Nope I only see one generated event in the system logs that matches up with the time stamp. Though I do get the following error: [nested exception is io.netty.handler.timeout.ReadTimeoutException. Exceeded maximum retry limit of 1] Which is weird as a bit of google fooing is saying that error should only be generated when it fails to send and receive a response within a certain timeframe, since I’m sending internally I would have thought that would be a 0 issue. ---
**Author:** ![maxkatz](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/maxkatz/32/5624_2.png) [@maxkatz](https://devforum.okta.com/u/maxkatz)\ **Post date:** [February 26, 2025, 5:50pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/4 "2025-02-26T17:50:45Z")
Hi @HennessyWorks, So yes, this shouldn’t be happening. I don’t know why it happens. You could try the following: 1. Turn the event hook off/on. 2. Create a new flow and use a new flow API endpoint with the event hook. 3. Create a new event hook and flow API endpoint. I guess these are similar to “restarting your computer.” I’m not a fan, but they might help. If you are still having this problem, please create a support ticket. ---
**Author:** ![HennessyWorks](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@HennessyWorks](https://devforum.okta.com/u/HennessyWorks)\ **Post date:** [February 27, 2025, 11:13am UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/5 "2025-02-27T11:13:43Z")
Yea annoyingly I have done all that, will reach out to Okta support, I did create a ticket ages ago (as we where very keen to use the feature) that’s how we have the workaround. But I would think if it’s been fixed and not intended, these new hooks/flows shouldn’t be acting this way. ---
**Author:** ![HennessyWorks](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@HennessyWorks](https://devforum.okta.com/u/HennessyWorks)\ **Post date:** [February 27, 2025, 4:26pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/6 "2025-02-27T16:26:36Z")
So just if anyone runs into the same issue. The fix can be found in the below KB: [https://support.okta.com/help/s/article/event-hook-sends-data-twice-to-workflows?language=en\_US](https://support.okta.com/help/s/article/event-hook-sends-data-twice-to-workflows?language=en_US) Seems like you must respond within the 3 second window and send a close. This will stop it from sending the event again. I feel like Okta should update this so if it’s an internal request it should be handled gracefully insidie the API Endpoint card. ---
**Author:** ![maxkatz](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/maxkatz/32/5624_2.png) [@maxkatz](https://devforum.okta.com/u/maxkatz)\ **Post date:** [February 27, 2025, 4:30pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/7 "2025-02-27T16:30:54Z")
Interesting. The platform should do that automatically for Okta events. Once you add the Close card, let us know if you no longer see the duplicate event. ---
**Author:** ![HennessyWorks](https://avatars.discourse-cdn.com/v4/letter/h/8797f3/32.png) [@HennessyWorks](https://devforum.okta.com/u/HennessyWorks)\ **Post date:** [February 28, 2025, 8:43am UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/8 "2025-02-28T08:43:09Z")
> [@maxkatz](#): > > Interesting. The platform should do that automatically for Okta events. I would have thought the same thing. But after adding the Close card I’m no longer seeing the issue I was on the flows that where leveraging the event hook. ---
**Author:** ![maxkatz](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/maxkatz/32/5624_2.png) [@maxkatz](https://devforum.okta.com/u/maxkatz)\ **Post date:** [February 28, 2025, 5:37pm UTC](https://devforum.okta.com/t/why-does-an-event-hook-send-multiple-requests/32324/9 "2025-02-28T17:37:11Z")
I’m glad it’s working. I will share this with the team.