Automation 360 Cloud Updates
Automation 360 Cloud is a multi-tenant cloud service that leverages the latest best practices in delivering web scale SaaS to rolling out incremental updates globally using a continuous deployment pipeline.
- If the bot tags data for Bot Insight.
- Parent / Child bots will run to completion as the child bots are downloaded at the start of running the parent bot. Unless the child bots are referenced using a variable parameter -calling those child bots need the Control Room to be available during parent bot runs.
- Bots using WLM.
Once the Bot agent has reconnected to the control room the bot status is updated in the Bot run activity logs.
Automated Bot agent takes place once an agent finishes any current bot run. Once update the agent reconnects to the Control Room.
During this short downtime, any bots scheduled to run will not be scheduled. It is therefore recommended that bots are not scheduled to start to run during the planned maintenance window.
|Region||Day Time in UTC|
|AP-AUS||Wednesday 12:00 to 16:00|
|AP-Sing||Wednesday 16:00 to 20:00|
|EU-West1||Tuesday 20:00 to Wednesday 02:00|
|EU-West4||Tuesday 20:00 to Wednesday 00:00|
|LATAM||Thursday 02:00 to 07:00|
|ME||Thursday 20:00 to Friday 00:00|
|S. Africa||Thursday 20:00 to Friday 00:00|
|US-East||Friday 02:00 to 07:00|
|US-Central||Friday 02:00 to 06:00|
|India||Friday 02:00 to Saturday 00:00|
|US-West||Monday 02:00 to 08:00|
|Canada||Monday 02:00 to 06:00|
|Japan||Monday 16:00 to 20:00|
Regular updates are planned approximately every 3 months and scheduled to occur during non-business hours and not close to the month end or beginning. Notifications are posted to the cloud status site 2 weeks in advance of the update. A notification message is also pushed to administrators in the Control Room in advance.
You can review changes in the release notes that are made available 3 weeks before each update.
Cloud Infrastructure Updates
Cloud infrastructure updates are carried out typically once per three month period. If these infrastructure updates involve planned downtime for Automation 360 Cloud, notifications are posted on the status site at least one week in advance.
Critical Patch Updates
Patch updates may be required for either critical security updates or where serious issues with an update impact the majority of cloud customers.
Any patches will require a maintenance window as described above. Typically, these would not require an agent update. As much notice as possible would be provided on the cloud status page.
Planned Maintenance Windows
|Type of updates||Frequency||Time expectation||Client action|
|Regular Automation 360 Control Room & Bot Agent||3-4 months||
4 hour window
~10 min downtime
|Bots can run to completion. Do not schedule bots to start during this 4 hour window.|
|Sandbox||4 weeks prior to regular cloud updates||Try new features out after the window. Sanity test production bots.|
|Cloud infrastructure||Once per 3 month period||Varies. Scheduled on weekends.||Bots can run to completion. Do not schedule bots to start during window|
|Critical Patch||As needed||Critical notice given ASAP|