Device is blocked from all services after exceeding device policies (for example, reaching its traffic limit).
You can restore service by adjusting the device’s policies.
In the emnify Portal Automations, this event is referred to as Device blocked.
The organization is blocked after exceeding the monthly cost limit (defined by emnify) or exceeding their prepaid balance (if not set up to be postpaid).
A device with a configured data limit has hit its warning percentage. This event gives you time to take action before any limits are reached or exceeded.
Example: If the data limit is 100 MB and the warning percentage is 80%, the system generates an event when the used volume exceeds 80 MB and the remaining volume goes below 20 MB.
You can configure the data limit and choose a warning percentage in the service policy settings. For more information on how configure limits via the emnify Portal, see Configure data and SMS limits. To use the emnify REST API, see Add data limit to service profile.
In the emnify Portal Automations, this event is referred to as Monthly threshold.
A device exceeded the daily SMS MO limit. By default, each device can send up to 5 peer-to-peer (P2P) SMS within a 24-hour interval. Afterwards, the messages are acknowledged but not forwarded to the final recipient and stored as failed.
The limit automatically resets 24 hours after the first message, and you still see all messages in your SMS console.
You are still charged for messages that aren’t forwarded due to this limit.
In the emnify Portal Automations, this event is referred to as Daily SMS limit.
The data limit for the device has been extended for the remaining duration of the month.
Example: The device limit was extended by 100 MB for the remaining duration of the month.