When something is down

Nothing is lost, in either direction

• WHMCS is down or unreachable when you reply. The reply is saved in the panel and you see a note saying it will be sent automatically. webticketer tries again after 30 seconds, then a minute, two, five, fifteen and thirty minutes, then every half hour, for a day. Replies to the same ticket are always sent in the order you wrote them.
• You change a status or close a ticket meanwhile. The change is saved here and passed on when WHMCS is back, with the ticket's status as it is by then.
• Customers write in WHMCS while webticketer cannot reach it. The next successful check brings in every new reply and ticket, and closes tickets that were closed there.
• The bot is offline. The panel is paused while the bot is offline, so nothing is changed in the dark; everything that was waiting is delivered and checked when the bot is back.

If a reply cannot be delivered for a day, or WHMCS refuses it for a reason that will not change (for example the ticket no longer exists there), it is marked as failed, and the ticket's activity list says “A reply was not delivered to WHMCS”. Send it again from WHMCS itself.

Credentials or the address stop working

If WHMCS starts refusing the credentials or the address, the card shows the reason and nothing is pulled in. Fix it in WHMCS (a new identifier and secret, or the allow list) and enter the new details in the card. Replies written meanwhile are still waiting and go out once it works, within the day.