Flux query timeout error reason differs between server logs and HTTP response on InfluxDB 2.x
I'm working with InfluxDB 2.x and trying to handle timeouts and cancellation consistently across the HTTP query API and write path. My goal is to reliably distinguish a server-side max-query-time termination from a client-side cancellation or a write timeout, but the error surfaces don't seem to line up. From what I can tell, a Flux query that exceeds the co
influxdb