Performance limits (Service Automation)
HelloID Service Automation is designed & tested to operate within the following maxima. It will operate above them, but performance may be degraded because individual HelloID customer tenants share server capacity. If your implementation exceeds them, please contact your local Tools4ever office.
Logging
All PowerShell scripts in Service Automation support logging (Logging in PowerShell product tasks); Logging in PowerShell data sources; Logging in delegated form PowerShell scripts; Logging in PowerShell scheduled tasks).
We suggest limiting the number of log messages per script execution. Excessive logging may decrease the performance of customer tenants.
Origin | Limit per execution | Example |
---|---|---|
50 messages |
| |
500 messages |
|
Scheduled tasks
Scheduled tasks are often used to sync users & groups from Active Directory to HelloID, or to sync Active Directory groups to HelloID products.
Origin | Limit per day | Comment |
---|---|---|
4 scheduled runs | These type of synchronization tasks are resource-intensive, because of the number of API calls and the typical business logic involved. Synchronizing large numbers of users or groups, or frequent scheduling of these tasks, can cause performance decreases in your HelloID tenant. In some cases, it may affect all tenants on the same server. | |
- | Please use caution with scripts that interact with the HelloID API, which may cause decreased performance. |
PowerShell script execution duration
The HelloID Agent has a secure & fast connection to the HelloID platform. To keep this infrastructure healthy, Agent connections are occasionally recycled. To avoid degraded performance, we suggest limiting the execution duration of your scripts.
Origin | Cloud Agent limit | On-premises Agent limit |
---|---|---|
5 minutes | 3 hours | |
5 minutes | 3 hours | |
5 minutes | 5 minutes | |
not supported | 3 hours |
API endpoints
You can interact with your tenant via the HelloID API. Although we don't currently enforce rate limits, we strongly advise you to use the API wisely and avoid making an excessive number of calls.
Data source output
Data sources are commonly used in delegated forms and products. We suggest only returning necessary data in data sources. Returning large amounts of data can decrease the performance of your HelloID tenant.
Test environment example: a dataset from a local Active Directory containing 9,000 user accounts (rows) and 7 attributes per account (columns) results in approximately 2 MB.
Origin | Limit per execution | Comment |
---|---|---|
2 MB | We suggest limiting the amount of data you query, and scoping or filtering it as much as possible, before returning it to HelloID. | |
100 KB | Static data sources are meant for small amounts of static data. | |
2 MB | Use the available filtering options (the Scope field in HelloID Users native data sources and the Name filter in HelloID Groups native data sources to limit the amount of data returned. |
Email notifications
Origin | Limit | Comment |
---|---|---|
- | Performance may be decreased if a large number of designated responders are emailed in a single approval step. | |
10 per execution | - |