# Client.Timeout or context cancellation while reading body events: body.payloads.map(payload)

**URL:** <https://discuss.elastic.co/t/client-timeout-or-context-cancellation-while-reading-body-events-body-payloads-map-payload/376605>\
**Category:** Elastic Agent\
**Created:** [April 1, 2025, 12:35am UTC](https://discuss.elastic.co/t/client-timeout-or-context-cancellation-while-reading-body-events-body-payloads-map-payload/376605 "2025-04-01T00:35:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![checo2024](https://avatars.discourse-cdn.com/v4/letter/c/b3f665/32.png) [@checo2024](https://discuss.elastic.co/u/checo2024)\
**Post date:** [April 1, 2025, 12:35am UTC](https://discuss.elastic.co/t/client-timeout-or-context-cancellation-while-reading-body-events-body-payloads-map-payload/376605/1 "2025-04-01T00:35:16Z")

</div>

After upgrading Elasticsearch to 8.17.4 (Windows), Elastic Agent and AbuseCH 2.6.1 integration the hosts listed in Fleet show unhealthy status. The logs show the following error :

elastic\_agent  
cel-default  
[elastic\_agent][warn] Unit state changed cel-default-cel-ti\_abusech-42d7e9ee-99cb-44b5-b4f6-51c61133514c (HEALTHY-\>DEGRADED): failed evaluation: failed eval: ERROR: :12:21: net/http: request canceled (Client.Timeout or context cancellation while reading body)  
| "events": body.payloads.map(payload, {

The AbuseCH has a new API key which appears to be working. Yet that error appears intermittently

Any thoughts in what might be causing that?

 ![Fleet-hostcomputer-integrations-status-2025-04-01_08-31-59-2](https://us1.discourse-cdn.com/elastic/original/3X/7/f/7ff017edf9fefb76c5a6221c874569f9b62eeb5c.jpeg)

Uploaded a screenshot of the error.

Thanks for your inputs.

 ![Timeout-AbuseCH-Integration-2025-03-31_17-15-34](https://us1.discourse-cdn.com/elastic/original/3X/9/0/90eb99c880e90fef00a8cfb7f463788b2a81969f.jpeg)