Agent Observability set to Disabled, causing errors (inconsistent behaviour)

vvgr001
Wed, 25 Feb 2026 15:35:33 +0000
Agents

Hi,

On one of our Cloud environments I have disabled Agent Observability on one of the projects in Livekit Cloud.

With some sessions we still get this error:

2026-02-25T15:12:02.774654966Z stdout F {“message”: “Failed to export logs batch code: 401, reason: \b\u0010\u0012+project data recording is disabled by owner\u001a+\n)type.googleapis.com/google.rpc.BadRequest”, “level”: “ERROR”, “name”: “opentelemetry.exporter.otlp.proto.http._log_exporter”, “room”: "call-

2026-02-25T15:11:37.3881419Z stdout F {“message”: “Failed to export logs batch code: 401, reason: \b\u0010\u0012+project data recording is disabled by owner\u001a+\n)type.googleapis.com/google.rpc.BadRequest”, “level”: “ERROR”, “name”: “opentelemetry.exporter.otlp.proto.http._log_exporter”, “room”: "call-room…

2026-02-25T15:12:27.632020767Z stdout F {“message”: “failed to upload the session report to LiveKit Cloud\nTraceback (most recent call last):\n File “/app/.venv/lib/python3.11/site-packages/livekit/agents/job.py”, line 265, in _on_session_end\n await _upload_session_report(\n File “/app/.venv/lib/python3.11/site-packages/livekit/agents/telemetry/traces.py”, line 505, in _upload_session_report\n resp.raise_for_status()\n File “/app/.venv/lib/python3.11/site-packages/aiohttp/client_reqrep.py”, line 636, in raise_for_status\n raise ClientResponseError(\naiohttp.client_exceptions.ClientResponseError: 401, message=‘Unauthorized’, url=‘******.livekit.cloud/observability/recordings/v0’”;, “level”: “ERROR”, “name”: “livekit.agents”, “exc_info”: "Traceback (most recent call last):\n File “/app/.venv/lib/python3.11/site-packages/livekit/agents/job.py”, line 265, in _on_session_end\n await _upload_session_report(\n File “/app/.venv/lib/python3.11/site-packages/livekit/agents/telemetry/traces.py”, line 505, in _upload_session_report\n resp.raise_for_status()\n File “/app/.venv/lib/python3.11/site-packages/aiohttp/client_reqrep.py”, line 636, in raise_for_status\n raise ClientResponseError(\naiohttp.client_exceptions.ClientResponseError: 401, message=‘Unauthorized’,

and with some sessions we don’t get this at all. Is this somehow related that the setting change needs to propagate in all the Livekit cloud nodes by any chance? We also see this behaviour is not consistent across all sessions?

6 posts - 2 participants