Bug fixing, handled

Page crashes, server failures, requests that fail behind the scenes and background jobs that go wrong are all recorded the moment they happen, with the technical detail our team needs attached. No volunteer has to witness it, describe it or even know it happened.

Every error is kept in two independent places, so running out of allowance at one provider doesn’t leave us blind. Repeats of the same fault gather on one ticket instead of burying each other.

The worst bugs never show an error message, and they are the ones people almost never write in about. So we watch for those too:

Our team is alerted automatically to brand-new problems, problems that come back after a fix, problems suddenly far louder than usual, and spikes across the whole platform. Then we fix them, as quickly as we can, and ship the fix to every club at once.

Anyone signed in can report a bug in one click: beside Help on every admin page, on their account page, or on the error screen itself. The page and recent errors travel with the report automatically, so nobody has to copy anything down.

Send it from an error screen and it joins the same ticket as the crash it describes, with a reference to quote if you ever need to follow up.

A fix is watched after it ships. If the same error happens again on a newer release, its ticket reopens by itself and our team is told. If an error marked fixed is still happening a day later, the ticket reopens regardless. A returning error doesn’t wait for your club to notice it a second time.

Screen replays are captured only around an error, never whole sessions, and text, inputs and media are masked by default. Member rosters, waivers and payment fields stay out of what our team sees.

Automated checks visit the platform around the clock, and check that our demo club’s public pages actually show content rather than merely respond. Live status for club websites, sign-in, online payments, email and custom web addresses is public on the service status page.