[ Akamai SIEM ] Integration stops after a 400 error and requires an agent restart to start working again.

Hello,

We are facing an issue with the Akamai SIEM integration where that for some reason it receives and 400 response code with the _"Invalid timestamp"_ information, when this happens the integration stops and requires an Elastic Agent restart to starting getting data again.

After the restart it will get older data based on the **_Recovery Interval_** setting.

This is the value of the `error.message` field:

```
"GET https://REDACTED.luna.akamaiapis.net/siem/v1/configs/REDACTED?limit=10000&offset=REDACTED{
""type"": ""https://problems.luna.akamaiapis.net/-/pep-authn/request-error"",
""title"": ""Bad request"",
""status"": 400,
""detail"": ""Invalid timestamp"",
""instance"": ""https://REDACTED.luna.akamaiapis.net/siem/v1/configs/REDACTED?limit=10000&offset=REDACTED"",
""method"": ""GET"",
""serverIp"": ""redacted"",
""clientIp"": ""redacted"",
""requestId"": ""redacted"",
""requestTime"": ""2026-07-14T13:25:51Z""
}
"
```

What could cause this Invalid Timestamp? Shouldn't the integration be able to recover from this?

Start with the Akamai SIEM integration and trace how it handles the reported 400 Invalid timestamp response and the Recovery Interval. Reproduce or inspect the failure path, then verify that the integration recovers and resumes collecting data without an Elastic Agent restart.

Written by the indexing model from the issue text.