Technical limitations of scripts

From Planfix
Jump to: navigation, search

Planfix scripts offer a wide range of capabilities for automating business processes. However, you need to remember that Planfix is a collaborative workspace, not a system for automating external operations like Zapier or Make. This also means that the pricing structure of the service is tied to the number of employees within the account, not the number of operations.

The service rates are calculated based on a workload of up to 200 operations per hour for each employee in the account. Such a workload allows the user to comfortably work in the system and use a branched system of scripts without experiencing delays in their execution.

Accounts that use Planfix for a purpose other than intended, especially for automatic (without user participation) processing of significant amounts of external data, cause an increased workload on the infrastructure, which can lead to delays in the execution of scripts for other accounts. To prevent such situations, we introduce automatic limitations for these accounts.

Limitation on the number of actions

Currently, the following limitations are in operation:

  • If automatic monitoring detects the increased activity of scripts in the account in the last hour that exceeds the limits equal to the number of account employees * 200, the account scripts start to be executed with a delay. This limitation allows all operations to be processed, although slightly slower, without significantly affecting the work of other accounts. Once the load peaks are smoothed out and the command processing queue is empty, the limitation is removed, and the scripts can work in standard mode.
  • If this limitation is insufficient and commands continue to pile up, execution of new scripts in that account will be suspended after the buffer is filled with 100,000 commands. This situation is extremely rare, similar to an "emergency valve" that allows the overall performance of the service to be maintained in case of increased workload due to a stream of external data being directed to a particular account. After the queue of command processing in the buffer is processed, the work of the scripts in the account is resumed.

Who is to blame and what to do

You can view the current state of script execution at any time on the panel Service quality testing panel.

Suppose the limitation on the number of scripts in your account is triggered regularly. In that case, it may indicate that it is being used unbalanced or not as intended (for automatic processing of external data, not for company teamwork in the system).

In this case, we recommend increasing the number of user licenses to increase the account's limits or reducing the workload (reducing the amount of external data that automatically enters the system and/or the number of scripts that process this data).

Go To