- Release notes
Integration Service release notes
April 2025
A major enhancement is coming to Integration Service. We are moving triggers into Orchestrator, to create a unified trigger experience. This move leverages Orchestrator's capabilities for editing and managing triggers, and brings the following benefits:
- Centralized management: Create, edit, and manage all types of triggers from a single location in Orchestrator.
- Enhanced control: Gain improved control over process execution, including robot-specific allocation and input argument management.
- Optimized performance: Benefit from features like automatic termination of long-running processes and dynamic process allocation.
Creating and managing new triggers will be available only in Orchestrator. During the transition period, you can continue to use the Triggers tab in Integration Service to manage your existing triggers. These existing triggers will be migrated to Orchestrator according to a planned schedule.
For details, refer to Triggers.
Timeline
- Existing Integration Service triggers will remain operational and visible in Integration Service until July 31, 2025. This date may be subject to extension.
- Following the migration, all existing Integration Service triggers will be transferred to Orchestrator. Consequently, the Triggers tab in Integration Service will be discontinued.
As part of ongoing efforts to improve our services, we are undertaking system maintenance for Integration Service across all tenants. The maintenance operation aims to migrate tenants using Integration Service to new Azure regions infrastructure.
Timeline
The migration is planned to start in early May 2025 and is expected to be completed by the end of that month.
We will notify you in advance of your scheduled migration. You will receive notifications seven days before and 24 hours before your migration.
Impact
The following components are included in the migration:
- Connections, both active and disabled.
- Event history – The event history for the 24 hours before the migration will be moved to the new region.
- Custom connectors.
- Triggers.
Once migration is completed for your tenants, you must update your company network allow list with the IP addresses specific to the new regions. For details, see Configuring the firewall in the Automation Cloud user guide.
- Disabled trigger for Slack Button Clicked. Reauthenticate to the Slack connector to re-enable the trigger.
- Failed connections for connectors that support single-authentication sessions. Create new connections to avoid process disruptions.
If you experience any issues, contact your account manager or UiPath Support.
We have upgraded the QuickBooks Online connector version to align with the latest version of the QuickBooks Online Accounting API. The Accounting API 1-74 minor version is scheduled to be deprecated starting with August 1, 2025, so the UiPath connector is now using version 1.75, to ensure continued compatibility.
We also addressed an inconsistency in error handling when connecting to the QuickBooks Online connector. Appropriate error messages are now displayed consistently for both Production and Sandbox connections.
Triggers can now retrieve and process datasets that exceed 1,000 records. Removing the record limitation for trigger executions ensures automations can process large datasets and capture all vendor records emitted within a configured time interval.
When creating a connection fails, we now display a comprehensive error message that indicates what API was invoked and the full error message coming from the third-party application. The detailed information helps you troubleshoot connection issues more effectively.
We've added a countdown timer to the connection creation screen, indicating the time remaining to complete the connection setup. Additionally, the Connect button is disabled when the session expires. This change is designed to improve connection success rates, particularly in cases where previous attempts failed due to session timeouts.
