# Unhandled Endpoint Response Code

**URL:** <https://community.nextw.com/t/unhandled-endpoint-response-code/1357>\
**Category:** Nextworld Platform\
**Tags:** Integrations\
**Created:** [October 16, 2025, 7:16am UTC](https://community.nextw.com/t/unhandled-endpoint-response-code/1357 "2025-10-16T07:16:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.lee](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/david.lee/32/331_2.png) [@david.lee](https://community.nextw.com/u/david.lee)\
**Post date:** [October 16, 2025, 7:16am UTC](https://community.nextw.com/t/unhandled-endpoint-response-code/1357/1 "2025-10-16T07:16:29Z")

</div>

I have an endpoint definition that has endpoint response codes config for 200, 201, 202, 400, 401, 500, and 502. However, I missed 404 and it is a valid response code for that endpoint. What would happen if the endpoint returns 404 back?

---

<div class="post-metadata">

**Author:** ![ian.p](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ian.p/32/427_2.png) [@ian.p](https://community.nextw.com/u/ian.p)\
**Post date:** [October 17, 2025, 7:42pm UTC](https://community.nextw.com/t/unhandled-endpoint-response-code/1357/2 "2025-10-17T19:42:23Z")

</div>

If a 404 was returned and had not been set up as a response code for the endpoint, I would expect the logic block would end up in the `Not Handled` pathway and you would see entries in `Endpoint Logging` something like this:

 ![image](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/1X/cf9a543734b9e5d8f469d77952218812b92e5c14.png)