Viewing Current Usage
To view an organization's current payload usage, first navigation to the organization's overview page. There is a widget in the right column that displays the device and payload count for the current billing period, along with a link to a detailed usage breakdown. That view can also be reached from the organization's
Settings section, under the
Usage sub-tab in the left column.
An organization's past payload usage can be viewed on each pay period's invoice. Navigate to the
Settings section, then the
Invoices sub-tab, and finally choose an invoice to view the usage during that period.
Your Sandbox usage for the current period is visible on the Sandbox page, which can be accessed in the top menu by clicking the
Organizations tab and selecting the
My Sandbox link. You may only view the Sandbox usage for the current period; historical Sandbox usage is not available at this time.
Though limits do not directly apply to applications, an application's current usage can be viewed on the application's overview page. This can, for example, help users determine which of their applications is generating large numbers of payloads and make adjustments to stay within your usage limits.
The following resources limits are strictly enforced. It is not possible to create additional resources within a Sandbox or organization without upgrading:
- Devices - This includes all device types, regardless of whether they connect to the Losant Platform
- Experience Users - This covers all experience users that exist within the owned applications
- Organization members - This includes current members (regardless of their role) and pending - but not expired - invitations
- Data Table storage - This is amount of data (in bytes) that can be stored across all of the account's data tables
Incoming and outgoing messages are each limited to 30 messages in a 15-second window (or, on average, two per second). If you exceed this limit, the device generating the messages is automatically disconnected.
An incoming message is typically a device reporting its state, and an outgoing message is usually a command being sent to a device.
For example, if one command is sent to 50 devices, the command only counts as one outgoing message against the message throttling limit, but it counts as 50 payloads against the payload limit.
Gateway devices are an exception to the message throttling rule, since they are responsible for all communication between the Losant Platform and their peripheral devices. For gateways, the message throttling limit is applied on a per-peripheral basis, meaning the throttling limit is applied individually to each peripheral.
For Sandboxes, the number of payloads generated by your applications is a hard limit, in that once the limit has been exceeded for the period, any payloads sent to or generated by the platform will be rejected. If you reach this limit, your options are to:
- Create a new organization and transfer some (or all) of your Sandbox resources into it
- Transfer some (or all) of your Sandbox resources into an existing organization for which you have administrator permissions
- Adjust your applications so that they generate fewer payloads, and wait for the payload period to turn over. Your payloads will continue to be rejected until the new period begins.
For organizations, the Losant Platform will continue to accept payloads after you have reached your monthly limit. However, payloads over that limit come with an additional cost. Depending on your chosen billing plan, these extra payloads cost anywhere between $5 and $10 per million payloads.
For current organization and Sandbox usage details, we also supply a message indicating if you are on pace to exceed that period's payload limit. This is based on the number of payloads per second generated during the period extrapolated over the course of the entire period. Therefore, if your payload usage dramatically changes, it may take some time before the changes are reflected in the prognosis.
We also supply a detailed breakdown of the number of payloads by type so that you can see where the majority of your payloads are accruing and make adjustments to your applications if necessary.
The following interactions count as a payload:
- A device reporting its state
- A command sent to a device
- Device connections to and disconnections from the Losant broker
- Workflow timer triggers
- Incoming webhook requests
- Incoming experience endpoint requests
- Incoming integration messages
- Workflow virtual buttons presses, including those triggered by an Input Controls block
- MQTT inbound and outbound messages (other than those listed above)
These interactions do NOT count as a payload:
- Losant event creations and modifications
- Data requests, including those made by Losant dashboards and device data exports
- Webhook replies in workflows
- Workflow runs triggered by another workflow
- Data table row insertions, deletions, edits and queries
Device state, device connection logs, and workflow logs within an application are subject to data retention age limits. Once data is older than the data retention limit, it is deleted. The data retention limit for an application varies depending on the plan level of the owning organization (or if the application is within a user's sandbox). See the Plans & Pricing table for details on the exact retention for each plan. If you need longer term data retention, contact us for an enterprise plan with customized data retention limits.
Other resources within the Losant Platform are subject to "soft limits." Though organizations and Sandboxes are subject to these limits when creating or transferring resources, you may request increases to these limits at no additional charge.
Soft-limited resources include: