Bugs found. Bugs fixed.

The pipeline that renders every trade card and updates this site runs a headless browser to draw the image. At some point its browser installation went missing from disk. Every run after that crashed.

What made it worse: the crash handler's own error-printing line choked on a Unicode character inside the error message, on Windows' console encoding. That second failure happened inside the except block, which meant it wasn't caught — it killed the entire script, every single run, before it could reach any bot after the first failure, or update this site at all.

Fix: reinstalled the browser, and reconfigured the script's output to tolerate any character so a future bad error message can never again take the whole pipeline down — worst case now, one card fails and everything else still runs.

On 2026-07-15, a partial exit left 2 units logged as still open, with no matching close event ever recorded for them. The card-generation logic tracked a running position balance across the whole trade log, and once that balance stopped returning to zero, it never completed another trade — for any position opened afterward, for three straight weeks — even though the pipeline ran every 30 minutes without a single error.

Fix: every new position open now always starts a fresh lifecycle instead of assuming it might be continuing a prior one, which matches how these bots actually trade and makes the tracker self-healing against this exact class of gap.

The Binance API requires every signed request's timestamp to be within a tight window of the exchange's own clock. The trading library exposes a timestamp_offset for exactly this — and never sets it. Local clock drift measured as high as 6.7 seconds in a single session, non-monotonically, not a slow steady creep.

Fix: sync the offset against Binance's public time endpoint on startup, plus a background resync every 30 minutes for the long-running process.

Every dashboard's trade table picked the row label from whichever field happened to be set first — and the field that was actually set (the specific action: open, partial exit, cover, stop) came second in that check, behind a generic field that's the same for every row on one side of a trade. The result: a single position's real lifecycle rendered as what looked like duplicate entries.

Fix: reordered the field priority so the specific action is read first.

The function checking whether a position was still open had a final fallback: if both of its lookups failed for any reason — including a transient network blip — it returned 0 units. That return value was indistinguishable from "confirmed flat," so a genuine API hiccup got logged as a real broker-side close, complete with a fabricated result.

Caught by cross-checking logged closes against OANDA's real transaction history — several had no matching fill at all.

Fix: the fallback now re-raises instead of guessing, so a real lookup failure is treated as "skip this check," not "the position is flat."