05-15-2024 07:23 AM
Based on the feedback from the customers and pain points that we heard from the partners, we have released the below 2 new platform accelerators:
No easy way for IT to check adherence to best practices.
No metrics to identify non-adherence to best practices.
No easy way for recipe builders to know whether they are adhering to internal best practices set by IT.
The Latest Version of AQS has a Completely Redesigned Rules Engine to Perform Quality Checks & Compile Quality Scores from an SDK for all the Rules to Reduce Execution Time & Task Consumption by the Accelerator. Additionally, AQS has unveiled a new SDK designed for Task Optimization Assessment. This SDK can systematically compile recommendations by leveraging insights derived from its predefined rules and core logic, ultimately reducing your task utilization. It significantly accelerates quality check time by 95% while reducing task consumption by 81%.
Would you like to see a demo for any of the accelerators? Get in touch with us through accelerators.feedback@workato.com
05-07-2025 02:27 AM
I’m currently implementing the Autonomous Operations Framework (AOF) from the Workato Academy, which is designed to standardize error handling, logging, and recovery using sub-recipes like error logging and job recovery. While testing the setup provided in the Academy package, I observed that the Job Recovery recipe is not being triggered, even though the conditional block in the orchestrator recipe explicitly passes "Yes" to invoke the recovery sub-recipe. I’ve confirmed that the orchestrator recipe calls the job recovery step as per the framework design, and the test scenario simulates a recipe failure, but the job recovery recipe still doesn’t appear in the dashboard or get executed. I’ve followed the AOF accelerator implementation without any customization, and all recipes are published and accessible. This seems to contradict the framework’s expected behavior, where job recovery should be automated once an error is encountered