Operations in the constructor

The cost of the plan in the constructor depends on the load on the server that each bot creates. Therefore, the pricing plans have a monthly transaction limit.  

Operation is any access to the server: sending a message, pressing a button, saving data to a table, etc. That is, the work of each block in the constructor takes operations. For example, one block with buttons will use up 2 operations: sending a block and pressing a button. If one person passes a survey of ten such blocks in the bot, it will take 20 operations.  

Transactions are accrued and updated on the date of payment of the plan. For example, if you paid the plan on September 12th, then the next time the transactions will be updated on October 12th. For a free plan – on the date of registration in the constructor. 

The number of available and expended operations can be viewed in the My Projects section. When the operations end, the bot stops working. The remaining transactions from the previous month are not transferred to the new one. If your bot has stopped, then after updating the operations, you need to enable scripts in the project.