Component: Robotic Process Automation

Resource	Service limit
Robot instance duration	4 hours
Assigning a robot instance to an environment timeout	Varies, depending upon the environments: If the environment pool contains no environments: 0 seconds, and then the status of the robot instance changes to Failed If the robot agent on the environment doesn't accept the request: 30 seconds, and then Oracle Integration attempts to assign the robot instance to a different environment If all environments in the environment pool have a status of Unavailable: 240 seconds, and then the status of the robot instance changes to Failed If at least one environment in the environment pool has a status of Available: No limit
File download timeout	180 seconds by default but the robot builder can specify a different value while creating a robot
File download size	50 MB
Polling frequency (frequency at which the robot agent polls Oracle Integration for work)	15 seconds
Maximum time that Oracle Integration waits for the robot agent to poll for work before changing its environment's status to Unavailable	35 seconds
Service instance data retention	Production: 32 days (default) for Standard and Enterprise editions, 184 days for Healthcare edition You can increase the data retention period for Standard and Enterprise editions if you want. See Edit the Data Retention Period. Audit: 8 days Debug (Not Recommended): 24 hours After 24 hours, a robot instance's Debug tracing level automatically changes to Production.
Environments in an environment pool	100 environments
Robot character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters
Environment pool character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters
Robot connection type character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters
Robot connection character limits	Name: 50 characters Description: 1,024 characters Keywords: 1,024 characters