Tracking the state of an instance#

Getting the state of an instance can be implemented in several ways:

1. Use the GetStateInstance method - request the state of the instance every minute and if the state of the instance changes perform actions:

   • authorized - inform the operator that the account is in a working state;
   • notAuthorized - inform the operator about the necessity to re-connect the account with the instance and stop requesting sending methods to the API (messages will not be delivered, they will be added to the queue and stored there for 24 hours);
   • blocked - inform the operator about the need to make a request to unblock the account and stop requesting sending methods to API (messages will not be delivered, they will be added to the queue and stored there for 24 hours);
   • starting - restart the instance using reboot method, wait for 2 minutes and repeat receiving the instance status, if the instance status has not changed, then inform the operator that the instance is currently in the startup mode and there may be a delay in sending messages;
   • yellowCard - inform the operator about receiving a warning on the account, it is required to follow the instructions specified in the article yellowCard. The account is partially or completely suspended from sending messages due to spammer activity. Messages sent after receiving the status are stored in the queue to be sent for 24 hours. To continue running the instance, you need to do a reboot of the instance.

2. Receive account status using notifications.
   To receive notifications you need to:

   • Enable the "Receive notifications when account authorization status changes" setting (using the setSettings method or via personal account).
   • Make a account status notification handler and when one of the statuses is received, perform the actions specified in the previous paragraph.