website logo
⌘K
Explore our documentation
Contact APIANT support
What is APIANT?
Automation Editor
Key Concepts
Account Management
Managing Automations
App Connections
Building Automations
Alert Mappings
Troubleshooting
CRMConnect: Mindbody → HubSpot
CRMConnect: DonorPerfect → HubSpot
CRMConnect: DonorPerfect → ActiveCampaign
MailConnect: DonorPerfect → Mailchimp
ShopConnect
ShopConnect Settings
Sync Products
Manually sync Mindbody services/pricing options to Shopify
How to tag products in Shopify to prevent sync during sales sent to Mindbody
Retrying orders from Shopify → Mindbody
Manually pushing Mindbody orders to Shopify
Mindbody Pricing Discontinuation: Integration with Shopify
Guide to manually syncing Mindbody Packages with Shopify Products
Features that are not supported in ShopConnect
Automation Alert Reports
Linked Accounts
ZoomConnect
New features in version 4
Settings
General
Email & SMS
BOTs
MINDBODY
Zoom
ZoomConnect Mindbody Appointments - Setup and requirements
Troubleshooting
Assembly Editor
Key Concepts
Account Management
API Key Management
Managing Content
Building Assemblies
API Integrations
Other Assembly Types
Keyvalue Storage
Assembly development cycle
APIANT for Integrators
Help Forum
Automation Templates
Development Server
Module IDE
Shared App Connections
Tenants and Linked Accounts
APIANT Inline
Supported functionality
Embed Inline
Sandbox
Docs powered by
Archbee
Automation Editor
...
Gear Menu
Processing menu

Concurrency

3min

Concurrency controls how many instances of the automation may run in parallel at the same time.

Generally, concurrency only applies to automations containing only webhook instant triggers.

For example, let's say an automation has a CRM "add person" instant trigger. And that the automation's actions take 10 seconds to do their processing for a single new person.

If 3 new people are added in the CRM in quick succession (say within a couple of seconds), the CRM will send 3 webhooks to the automation.

If the automation's concurrency limit is set to the default of 1, then each of those 3 person records will be processed one after another, in a total of 30 seconds.

If on the other hand the automation's concurrecy limit is set to 3, then each of those 3 person records will be processed at the same time, in a total of 10 seconds.

Concurrency can also be relevant to automations without any instant triggers in the event an automation having webhook instant triggers invokes another automation via an "execute automation" action.

To change an automation's concurrency limit, select the menu option under the Processing menu:

Document image


Then configured the new limit:

Document image


Whether or not the system can actually process the automation to its maximum configured concurrency limit will depend on the system's resources, including the load of other automations being processed and the system's configuration.

API calls within actions will usually have their own concurrency limit. When actions exceed an API's concurrency limit, usually the API will return a 429 HTTP status code meaning that the API's rate limit was exceeded. So setting an automation's concurrency limit too high for the actions it uses can cause the automation to begin to report errors. There is no free lunch!



Updated 03 Mar 2023
Did this page help you?
PREVIOUS
Alert email options
NEXT
Disabling data storage
Docs powered by
Archbee
Docs powered by
Archbee