---
title: "Cloud Status"
slug: "cloud-status"
updated: 2025-01-31T13:57:18Z
published: 2025-01-31T13:57:18Z
canonical: "learn.servitly.com/cloud-status"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.servitly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud Status

Identifies the thing activation status that is used to determine if a Thing can communicate with the cloud or not. A new status is automatically registered within the Cloud Status metric each time the cloud status changes, for instance, the thing has been activated or deactivated.

Note that the cloud status metric is only used to access historical status values, while the actual status is the one saved on the object as a property.

The metric is of integer type, and each value returned corresponds to a precise status.

| **Value** | **Meaning** | **Description** |
| --- | --- | --- |
| 0 | *INACTIVE* | Incoming IoT data is discarded, events and other periodic computations are stopped. |
| 1 | *TEST* | Similar to ACTIVE, but with some limitations; see the following section for details. |
| 2 | *ACTIVE* | The thing can publish data, and it is counted in the billing. |
| 3 | *~~SUSPENDED~~* | This status is deprecated and no longer used. |
| 4 | *PROVISIONING* | The thing initial status when created. When done, the status is automatically changed to ACTIVE. |
| 5 | *ACTIVATING* | The thing is about to be activated. When done, the status is automatically changed to ACTIVE. |
| 6 | *ACTIVATING_TEST* | The thing is about to be tested. When done, the status is automatically changed to TEST. |

> [!NOTE]
> Temporary statuses
> 
> *PROVISIONING*, *ACTIVATING* and *ACTIVATING_TEST* are transient statuses, and for this reason, not saved in the cloud status history.

## TEST Status

It is a special cloud state that precedes the *ACTIVE* state, and allows you to verify that the things registered in the DPS can communicate correctly with the cloud.

Things with this state can send IoT data, and receive remote commands or updates. Computed metrics, events, and notifications work in the same way as for *ACTIVE* things.

The number of things in *TEST* is limited and is defined in the commercial offer.

Data collected in this state are retained even when the object switches to the *ACTIVE* or *INACTIVE* state.

Things in *TEST* are not counted in the monthly bill.

In the DPS, by entering a thing in *TEST*, you will see a disclaimer. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(673).png)

# Predefined thing Properties

Other than the metric, on each thing object there are two additional properties:

- *cloudStatus*: the last registered cloud status value for the thing.
- *cloudStatusLastUpdateTimestamp*: the timestamp related to the last cloud status change.

You can reference these properties into widgets. Here is an example of [Thing List](/docs/thing-list-widget) showing also the Cloud Status.

```xml
<thing-list-widget-v2>
  <property name="name"></property>
  <property name="serialNumber"></property>
  <property name="cloudStatus" filter="cloudStatus"></property>
</thing-list-widget-v2>
```

These properties are also available via API or into Algorithms computation.