All tenant status pages are accessed in the same manner:
Each environment is accessed by changing the subdomain accordingly.
The response of each endpoint contains the context identifier, endpoint, functional state, whether the tenany is running or not and when the tenant infomation may expire.
All possible values are listed in the following table.
||Context identifier like Cust00000
||Root path of customer installation will change from time to time, from "https://sod2.superoffice.com:443/Cust00000 "https://sod3.superoffice.com:443/Cust00000. Changes occur routinely to balance load and/or under special circumstances like incidents.
Customer is unknown, or there is something wrong with the environment. If the customer was previously in another state, we probably have an incident of sorts.
||We are in the state of provisioning the customer. Should be ready in a short time.
||Customer is running. All is good.
||Customer has been deleted, forget all about it.
||Customer is in termination. API’s are not available, and the customer can still take action to reactivate his subscription. Resuming a customer in termination typically occurs at night or by manual activation by the sales team.
||We are performing background tasks, but nothing preventing customer for performing normal operations. API is available. Background tasks might take some time before they start.
||Customer is offline for maintenance. This typically happens during upgrade. It usually take minutes for the customer to be online again. API’s are not available.
||Provisioning has failed.
||We are in the process of deleting the customer. Expect the customer to be deleted shortly.
||Deleting the customer failed. Expect the customer to be deleted in a while.
||This is a new migration to online that has not yet completed. Expect the customer to be Running at a later time. Customers are often in state MigrationPending for days or weeks.
||Customer state is Running or OnlineMaintenance. This indicates that API’s are up and running and all is good.
||When to check next time if an updated state is needed.
All applications should leverage the status page to ensure their applications and integrations remain stable and respond accordingly.