You can now add comments to every workflow version created during updates. This helps document what changes were made and provides valuable context for collaborators reviewing the workflow. These comments also make upgrades and rollbacks in release management easier by allowing quick identification of version history and intent.

You can now visualize how resources depend on one another with interactive, drag-and-drop dependency graphs. These graphs allow you to explore dependencies across assets—drilling down infinitely to understand relationships in precise detail.

Select any resource from the dropdown to view its full dependency chain, or explore dependencies for a specific Journey directly from its Journey page. A convenient “Go to Asset” button lets you navigate to any referenced asset with a single click.

Users can now include additional team members in Journey failure notification emails, allowing stakeholders across the workspace to stay informed alongside the account owner. Only users who are part of the workspace team can be added, and if a team member is removed from the workspace, they will be automatically removed from the notification settings as well.

We have streamlined the connector deployment experience for on-premise environments using Quickwork’s proprietary serverless compute stack. Administrators can now access the full library of apps directly from the Backoffice portal and deploy, scale, upgrade, and patch connectors—all from a single, unified interface complete with telemetry and logs for each connector.

Every connector is also distributed with its own signed SBOM, security scan reports, and publisher certification, ensuring transparency, security, and trust for on-premise installations.

Telemetry is now available at the Journey level for all users of APIM, CDC, and Provisioned Concurrency. This enhancement allows users to access detailed, context-specific metrics directly within each Journey.

An aggregated telemetry view will soon be introduced in the dashboard to provide a unified overview across all Journeys.

Metrics are contextual, meaning they automatically adapt based on the type of Journey—displaying only the most relevant data for that configuration. Users can also customize the time range and granularity of their view to identify trends and performance patterns more effectively.

Quickwork’s Single Sign-On (SSO) support is now generally available for all Enterprise users and can be configured directly from the Admin Portal.

Quickwork supports multiple authentication mechanisms, including SAML, IDP, and OAuth-based authentication. In addition, administrators can enable an extra two-factor authentication (2FA) layer on top of the existing authentication setup for enhanced security.

Quickwork’s AI Agents now support a wider selection of Google Gemini LLM models, giving users access to the latest advancements in AI performance and capability.

Previously supported models that have been deprecated are clearly marked, and any deprecated models currently in use will be automatically upgraded by Quickwork—no action required from users.

Quickwork now supports enforcing order guarantees at the journey level, ensuring that transactions are processed sequentially with full idempotency. This means requests—whether received via polling or webhooks—will be executed in the exact order they arrive.

While order guarantees can be enabled for API services as well, this is not recommended, as it may delay independent API calls that don’t depend on each other.

Once enabled, metrics related to the wait queue will automatically appear in the monitoring section, providing better visibility into ordered execution performance.

Quickwork now supports Change Data Capture (CDC) triggers for popular databases, including PostgreSQL, MongoDB, DynamoDB, and MySQL, with additional database support coming soon.

This capability enables seamless real-time data synchronization by capturing and processing data changes as they occur—either as individual events or in batches of thousands. Quickwork ensures strict ordering guarantees, so every change is captured and processed exactly in the order it was received.

Additionally, users gain access to detailed telemetry and performance metrics for each CDC Journey, including ingestion rate, processing rate, and queue depth, providing complete visibility into data flow performance and reliability.

Quickwork now supports on-premise installation of the complete platform—including all connectors and services—through either Helm Charts or the KOTS UI interface for simplified deployment and management.

Both deployment methods include enhanced preflight checks to ensure consistent and reliable setup across environments. These options are available for air-gapped and non-air-gapped deployments, allowing organizations to choose the most suitable installation method during license issuance or enable both for maximum flexibility.

While Helm Charts provide greater customization for advanced configurations, KOTS offers a more streamlined, UI-driven experience—giving users a balanced choice between simplicity and control.