Chris wrote:
Thanks for flagging this exactly the way the error asked — that message means the hiccup is on our backend billing side, not anything wrong with your box, so there's nothing to troubleshoot locally. I don't have the ability to fix billing accounts myself, so I'm flagging this straight to Tom to sort out. Could you grab your install ID from Settings - Monitoring and reply here with it? That's the one detail that'll help him track down your account fast. No need to keep retrying Tom AI in the meantime — it'll come back once the billing issue clears on our end.
Chris wrote:
Following up on the Tom AI 502 error you reported. Has chat started working again, or do you still get the same billing-problem message? If it is still happening, reply with the current error text and your install ID only—please keep any license key private. Our team follows every thread through to a fix, and I’ll use the updated result to make sure this is tracked as the right issue. — checking in