Workflow execution  

• A maximum of 120 workflow action calls (requests) can be executed per minute and per IP address. This count includes the execution of the following:
  

  • Script in the on load form event

  • Script in the on user input form event

  • Script in the subform add row form event

  • Script in the subform delete row form event

  • formula field's expression

  • Lookup field's filter (when it uses another field in that form)

  • Deluge script behind button click (when it's a stateless form)

• The action calls limit for an app in an account is 250 requests per minute. This is a collective of multiple users accessing same action request.

• The action calls limit for a portal in an account is 250 requests per minute. This is a collective of multiple users accessing same action request.

• The action calls limit for a portal in an account is 250 requests per minute. This is collective of multiple users accessing same action request.

• In blueprints, the maximum number of statements that can be executed in one change stage function and execute transition function is 50.

• Note: A statement refers to one task as a whole. For example, the entire "if" condition will be considered as a single statement

• In deluge scripts, the maximum number of statements that can be executed in one function is approximately 5000 to 50000, depending on your pricing plan. 

Batch Workflow

1. This workflow is currently not supported for integrations forms.
   
2. Users can create up to 5 variables within a batch workflow.
   
3. Only one batch workflow can be executed concurrently for an account (based on creation date). This means that additional batch workflows will be queued for execution, thereby ensuring fair resource allocation and preventing overload on system resources.
   

1. The "old" keyword is not supported in batch workflows.
2. Info message cannot exceed 50KB. Otherwise, the message will be truncated.
3. The maximum size of file attachments allowed is 15 MB. If the attachments exceed this limit, the emails will be delivered without them.
   
4. If you want to get the content of the specified file or create a file object using the required content, the respective file size should be less than 2 MB.
5. getUrl() and postUrl() tasks are currently not supported.
6. You cannot assign values to global variables. You can still access them using info statement.
   
7. The operations for fetch with range and delete are limited to a maximum of 5000 records. 
8. The following Deluge operations are not supported in batch workflows. 
1. Fetching all values of a field
   
2. Using aggregate functions (except distinct) on fetched records
   
3. Using getall built-in function
4. Client functions 

Note:
The above mentioned restrictions will also apply to function calls triggered from batch workflows.

Batch workflows can be used to overcome the Deluge script limitation of executing only 5000 statements per function.

Send Mail Task         

• '\n' in the message content of 'plain text mail' will be rendered as a newline character.

• Attaching reports using send mail task is not applicable for published forms.

• You can attach up to 15 MB of data in send mail tasks. Learn More
  
  

Email Notification          

Note: As per Gmail's new policy, sender email addresses containing gmail should be  domain verified before use.

Blueprints 

• Number of stages and transitions that can be created is 100 per blueprint

• Number of common transitions possible in a blueprint is 5

• Number of parallel transitions possible in a blueprint is 5

• Number of branches in a parallel transition is 5

• Number of transition per parallel is 5

• Number of parallel transition between stages per direction is 1

• Number of outgoing parallel transitions per stage is 2