fix: suppress spurious 'api_token id=undefined not found' error on lastSeen flush

[livepeer-tessa]

Problem

staging-livepeer-api has been logging this error ~18 times in the last 12h, roughly every 30–60 min:

error saving last seen: table=api_token id=2f25c979-904f-4fce-b329-4174b54fdcbf err= Ge [Error]: api_token id=undefined not found

Root cause: In tracking.ts, flushLastSeen() calls table.update() with an array of SQL conditions (not a plain id string). When the UPDATE matches 0 rows and throwIfEmpty=true (the default), table.ts constructs the error message using doc.id — but doc is the partial update payload { lastSeen: <timestamp> } with no id field, so doc.id is always undefined.

The real UUID is correctly logged at the call site (visible in the log output), but the NotFoundError message itself reads id=undefined.

The UPDATE returns 0 rows because the second condition in the WHERE clause:

coalesce((data->'lastSeen')::bigint, 0) < ${lastSeen}

...is false when the stored lastSeen is already >= the value being flushed (race between multiple concurrent requests for the same token). This is expected/benign behaviour.

Fix

Primary fix — tracking.ts: Pass { throwIfEmpty: false } to table.update() for lastSeen updates. These are best-effort bookkeeping — a no-op UPDATE (token deleted, or lastSeen already up-to-date) is not an error and should not throw.

Secondary fix — table.ts: When query is an array, use the id from the query context ((doc as any).id ?? '(unknown)') rather than doc.id, which is never populated in this call path. This prevents the misleading id=undefined in any future error messages from other callers of update() with array queries.

Impact

• Staging only (no prod occurrences observed)
• Token auth continues to work fine (SELECT queries succeed)
• Fix eliminates spurious error log noise; no functional behaviour change

Closes daydreamlive/scope#761

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
livepeer-studio	Ready	Preview, Comment	Mar 30, 2026 6:28am