API Task FAQs

Review the FAQs to learn more about API Tasks.

How does an API Task execute compared to a Task Bot?

API Tasks execute in the Automation 360 Cloud, unlike Task Bots, which use the bot runner devices on the customer's infrastructure. API Tasks do not perform desktop interactions like Task Bots and can start quickly and potentially run faster than Task Bots.

In addition, the product is General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA) compliant. API Task is also part of the platform that is SOC 2 compliant. All API Task data is encrypted and we also provide encryption for both moving and static data.

Do API Task support custom packages created using the Package SDK?
No, API Task does not currently support packages built using the Package SDK.
If one of the devices goes down in my API device pool, would another be spun up automatically?
Yes, everything is managed for you.
What is the lifespan of the devices that spin up?
Your API device pool's resources are available for the duration of your configuration.
Does anything need to be set up on the deployment machine?
API Tasks execute on the Automation 360 Cloud devices; therefore, no customer devices on their infrastructure need to be set up.
Do I need to perform any device installation?
Cloud devices run on clusters managed by Automation Anywhere. There is no device installation required by the customer.
Is there a timeout for the API Task execution?
For real-time API Tasks, the timeout is 1 minute. For on-demand API Tasks, the timeout is 15 minutes..
What kind of data and for how long does the information persist on the cloud devices?
Transient data does not persist; only the API Task metadata is saved.
Why the run option is not available in the API Task editor?
The API Task editor does not have the run option as an API Task cannot be deployed individually. You must invoke the API Task in a form or process. Then run the process to deploy the API Task.
How do I find errors in my API Task?
To verify if your API Task logic is correct, you can use the debugger tool and watch the output variables. You can also use the error handler package actions to check for any errors in the API Task.
What is pre-warming?
Pre-warming is the process of pre installing the API Task logic and commands on Cloud devices preparing it to handle incoming requests. During warming, all API Task dependencies including libraries are installed beforehand. This is beneficial since it eliminates the need to check for dependencies before deploying the API Task. Hence, API Tasks run with very low latency. API Tasks that are invoked in a form must be pre-warmed on a Cloud device for it to execute successfully. Before you execute a process that has the form (API Task attached), you can check if the API Task is pre-warmed in the audit logs. For more details, see View API Task run time audit logs.
What is the license model for API-Tasks?
Every cloud customer receives 100 API Task executions per Control Room as their free base entitlement. The base entitlement also includes two concurrent executions, meaning you can run two API Tasks simultaneously. For higher execution limits and additional concurrencies, you need to purchase the Enterprise Platform SKU or an API Task Overage SKU. Contact your customer service manager for more details.