# When is an error definitely a permanent failure?

**URL:** <https://discuss.elastic.co/t/when-is-an-error-definitely-a-permanent-failure/384083>\
**Category:** Elasticsearch\
**Created:** [December 15, 2025, 3:10pm UTC](https://discuss.elastic.co/t/when-is-an-error-definitely-a-permanent-failure/384083 "2025-12-15T15:10:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Mo\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mo_b/32/146040_2.png) [@Mo\_B](https://discuss.elastic.co/u/Mo_B)\
**Post date:** [December 16, 2025, 8:24pm UTC](https://discuss.elastic.co/t/when-is-an-error-definitely-a-permanent-failure/384083/6 "2025-12-16T20:24:26Z")

</div>

By permanent failure I mean that resending the exact same request would produce the same error. Basically, I was mainly unsure about 400 (Bad Request) which I thought only happened for genuinely bad requests, but Claude AI stated it could possibly also happen due to timeout. So I guess it's plainly wrong, and 400 really means it's non-retryable? Maybe it got confused because of this thread: [X-Pack -"Monitoring: Error 400 Bad Request: Request Timeout after 60000ms"](https://discuss.elastic.co/t/x-pack-monitoring-error-400-bad-request-request-timeout-after-60000ms/84808)

---

_[View the full topic](https://discuss.elastic.co/t/when-is-an-error-definitely-a-permanent-failure/384083)._