What happens when the game changes and the bot breaks
It will break. Not as a defect — as a property of the thing. Anything that automates a website you do not control is downstream of decisions someone else makes without telling you. The useful question is not whether, it is what happens next, and that is a question most tools quietly avoid answering.
What actually breaks, in order of likelihood
Page structure. A button moves, a form field is renamed, a table gains a column. Anything that reads the page by looking for text or position breaks here first — which is why reading by structure rather than by visible wording matters more than it sounds.
Endpoints. The address an action posts to changes, or starts demanding a parameter it did not need before. This breaks loudly and immediately.
Language. A page shipped in a language the automation was not reading for is functionally the same as a page that changed. This is a real and frequently underestimated cause of "it stopped working for me but not for you".
The dangerous failure is the quiet one
A bot that crashes is annoying. A bot that keeps running while doing nothing is expensive, because everything looks fine — the app is open, the log is moving, and hours pass with no progress at all. The design decision that matters is what happens on repeated failure: an account that stops and reports costs you an evening; an account that keeps retrying a broken action can cost you far more, and it will not tell you.
That is why there is a circuit breaker: after a run of failures the account is halted rather than left hammering, and the reason is recorded instead of buried.
How you find out — and how fast
Fixes ship as ordinary releases, typically one or two a month, with urgent breakage handled faster — the stated target is 24 to 72 hours for a hotfix once the cause is understood. Announcements go to Discord and the changelog, and the app itself tells you when a newer build exists.
The honest part: "once the cause is understood" is doing real work in that sentence. A change that only affects some servers, or only some languages, is discovered when someone reports it — which is the argument for reporting things rather than waiting.
What this does not promise
- There is no uptime guarantee, and there could not honestly be one: the thing being automated is not ours.
- You will lose some hours. Between a change landing and a fix shipping, the affected accounts are stopped. That is the correct behaviour, and it is still a loss.
- The free tier carries no promise of priority. Paid tiers get support channels; the free tier gets the same fixes, not a faster queue.
- A rewrite on the other side can take longer than 72 hours. Small changes are quick. A redesign is not a hotfix.
Why we say this out loud
Every automation tool has these limits. The ones that do not mention them are not more reliable — they are less specific. Knowing in advance what breaks, what the bot does about it, and what you are owed is the difference between a bad evening and a refund request.
Try it free for 30 days What an overnight costs
No card required. The free tier stays free.