Urgent.News

What's breaking now, across thousands of outlets.

Tech

Our code silently replaced our own $50 daily loss limit with $142

The short version: we set a hard daily loss limit of $50. For at least the 42 trading days we can measure, the number actually running was about $142. Nothing crashed. No alarm fired. The logs were clean. We found it by hand, weeks later, by comparing what we had written down with what the machine had actually done. "Daily loss limit" in plain words: a ceiling on how much the account may lose in…

The short version: a $50 daily loss limit was silently overridden by the bot's code to $142 over 42 trading days. This undisclosed bug went unnoticed as the logs showed no errors, even though the account experienced a worst single day loss of $100.26, which is still below the $142 limit. The issue was discovered by comparing the configured limit ($50) against actual account performance (5 out of 42 days closed worse than $50).

The fix involved updating the code to always choose the stricter limit between the calculated daily cap and the rule value.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

IdP Logout in an SPA

Sequence Confirm and quiesce. The user confirms logout. The shell first instructs every embedded child application to log itself out and waits until all of them report completion.

More from Friday 9 October →