[helgehoi]

Ticket

VI-5068 — [tamstool] Upgrade TAMS Store Browser to TAMS 8.2

The bug

Against an 8.2 store, /#/embed logs a 400 every 5 seconds:

GET https://…/flows/2928d8bb-…/?include_timerange=true&_t=1787786076960  400 (Bad Request)

Why

The growing-flow poll appends a cache-buster:

await api.get(`/flows/${flowId}?include_timerange=true&_t=${Date.now()}`);

added in 98ebed4 to bypass API Gateway and CDN caching. A TAMS 8.2 store validates query parameters and rejects the unknown _t with a 400, so every one of those polls has been failing against such a store — invisibly, since the loop ends in catch { /* skip */ }. It is part of why duration and LIVE never moved on a growing flow before #25.

The same request without the parameter is what the re-check path in #25 already issues, successfully, against the same store and the same flow — which is the direct evidence that _t is what the store objects to.

The parameter was not earning its place in the browser either: api.get already fetches with cache: "no-store".

The fix

Drop it. No replacement header — Cache-Control is not CORS-safelisted, and adding one would put the request at the mercy of each store's allowed-headers list for a problem no-store already covers.

Testing

• npm run build passes (Node 22, same as CI)
• The failing request is the reporter's own console output; the working variant is the URL VI-5068 Re-check embed sources on a timer, not on the source listing #25 already issues against that store

🤖 Generated with Claude Code