Organizations and Sandboxes within the WEGnology Platform are subject to limits on the number of resources (e.g. Devices, Applications and more) that are registered under that entity.
Viewing Current Usage
To view an organization’s current payload usage, navigate to the Organization’s overview page. There is a widget in the right column that displays the device and payload count for the current period, along with a link to a detailed usage breakdown. That view can also be reached under
Usage in the application menu column.
Your Sandbox usage for the current period is visible on the Sandbox page, which can be accessed 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 WEGnology 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 mqtt messages are each limited to 30 messages in a 15-second window (or, on average, two per second) per topic, and 300 messages in a 15-second window (on average 20 per second) per connection. If you exceed these limits, the device generating the messages is automatically disconnected, and will not be allowed to connect back to the broker for 30 seconds. If a device repeatedly exceeds these limits, the length of time the device is not allowed to connect will increase, up to a maximum of one hour.
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 WEGnology Platform and their Peripheral Devices. For Gateway Devices, the message throttling limit is applied on a per-peripheral basis, meaning the throttling limit is applied individually to each peripheral.
Event creation is limited to 15 creations in a 15-second window per application (or, on average, one per second).
Other resources within the WEGnology Platform are subject to “soft limits.” Though Organizations and Sandboxes are subject to these limits when creating or transferring resources, Organizations may request increases to these limits for potentially no additional charge.
Soft-limited resources include:
- Access Keys
- Application API Tokens
- Data Tables
- Device Recipes
- Experience Endpoints
- Experience Groups
- Experience Views
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 WEGnology Platform will continue to accept payloads after you have reached your monthly limit. However, payloads over that limit come with an additional cost.
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 Broker or via the REST API
- 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:
- WEGnology event creations and modifications
- Data requests, including those made by WEGnology dashboards and device data exports
- Webhook replies in workflows
- Workflow runs triggered by another workflow
- Data table row insertions, deletions, edits and queries
Once data is older than the data retention limit, it is deleted. The data retention limit for an application varies depending on your platform license (or if the application is within a user’s Sandbox). If you need longer term data retention, contact us for an enterprise plan with customized data retention limits.
The following resources are subject to your Organization or Sandbox data retention limits:
- Device state
- Device command
- Device connection logs
- Workflow storage (however, retention resets on both key read and write operations)
In addition, the following data is subject to custom limits, regardless of your organization’s data retention limit:
- Workflow metrics (errors, run counts, and run time calculations) are stored for 30 days.
- Experience Endpoint request counts are stored for 30 days.
- Detailed payload count metrics are stored for 90 days.