October 2020

As of now, API operations in your Orchestrator services no longer require the logical name of the tenant as the entire process has been stripped down to only using the tenant display name. Worry not, we preserved backward compatibility for all of you out there still using the logical name when consuming cloud APIs.

Learn how to consume APIs in Automation Cloud.

Learn about API Access.

Starting now, a trigger gets disabled automatically after 10 failed launches if it hadn’t been successfully launched in the last day.

As of now, Orchestrator parses and preserves special characters by default and no longer uses encoding and escaping mechanisms to transform input data for dynamic properties in OData models (e.g. QueueItem.SpecificContent).

If your automation projects are designed to overcome character encoding/escaping any other way than using the method presented above (such as Regex unescaping expressions), make sure to adjust them accordingly as they might not work from now on.