Changelog
Keep up with the latest updates we’ve made in Workato.
Export job execution history to CSV
You can now export up to 1000 rows of job history from the Jobs tab, to aid in compliance or data analysis efforts. The row count does take into account any filters applied.
Addition of package id to the package deployed RecipeOps trigger
To make it easier to work with projects after deployment, the RecipeOps trigger now includes the package_id. With this package_id, you can confirm which recipes were deployed via API.
Sort manifest list on export and import pages
When viewing your exported and imported manifests within Recipe Lifecycle Management, you can now sort the page based on either latest activity, or A > Z to find manifest packages more quickly.
Addition of “connection lost” values to the Embedded API connection methods
When interacting with the Embedded API connection methods, there are now two values returned to help understand when and how a connection was lost: connection_lost_at and cconnection_lost_reason.
Expansion of Developer APIs for connector management
New endpoints have been added to expand the resources of the developer API, with connection management in mind. Read more about the new endpoints in our documentation:
Updates to time filters on job history and deployment tabs
On the deployments tab, additional time filters are now available for enabling users to see deployments history beyond 30 days.
On the job history page, the time range now defaults to last 30 days.
Job and Recipe Developer API Enhancements
New fields have been added to the following endpoints:
- Get Job (Developer API / Embedded API) API endpoint have new error fields for additional visibility when troubleshooting jobs - error count, step, app, action, and retry count
- Create Recipe (Developer API / Embedded API) and Update Recipe (Developer API / Embedded API) API endpoints have a new field to update the recipe description
Addition of RecipeOps trigger for alerting when API client exceeds policy limit
The new Recipe Operations triggers for policy quota and rate limit violations are instrumental in giving administrators visibility and the ability to proactively monitor their client's API usage. With these new triggers, administrators can now receive active alerts about violations, and move quickly to address.
Audit log streaming email error notifications
When audit log streaming fails, Workato now sends email notifications to the workspace admin of your account and to all users designated in the error notifications email list. For Embedded accounts, email recipients are determined based on the workspace where audit log streaming is enabled.
Email notifications will be sent for the following error types:
- Voluntary disconnections by a user
- Involuntary disconnections, when Workato detects we no longer have access
- Destination-specific errors
Audit log streaming retry
In the event Workato is unable to stream a log to the specified destination, Workato will retry sending the log repeatedly using an exponential backoff formula. To enable this, logs are kept in a persistent cache until:
- The audit log reaches its destination successfully, or
- Seven (7) days have passed.
Each retry attempt is logged in the Workato Logs service for visibility into the process.