AOF Framework: Job Recovery Recipe Not Triggering After Failure in Main Orchestrator

[Patel0786]

Hi Community,

I'm implementing the Workato Autonomous Operations Framework (AOF) in my workspace, following the standard 4-layer structure:

Business Logic → Error Handler → Logging → Job Recovery

I'm using the official AOF package provided by Workato Academy, and I've followed the recipe structure and configurations exactly as downloaded.

Here’s the issue I’m facing:

• In my main orchestrator recipe, I intentionally throw an error to simulate failure. This correctly triggers the error handler recipe via Call recipe.

• The error handler logs the error and then conditionally triggers the job recovery sub-recipe based on a conditional block.

• The conditional block came pre-configured from the AOF Academy package with a default value of "Yes" (under the condition to execute job recovery).

• However, despite this setup, the job recovery recipe never executes — it doesn’t appear in the job dashboard at all.

📸 Flow Overview:

• Image 1: Job dashboard showing no trace of the job recovery recipe being triggered.

• Image 2: Main orchestrator recipe where error handler and recovery recipe are referenced.

• Image 3: Test execution confirming failure, but no recovery call was made.

• Image 4: My AOF flow diagram (intended full structure).

🔍 What I’ve Verified:

• The recovery recipe is active and callable.

• The input/output schema between recipes is configured.

• The condition in the error handler is present as per the Workato Academy template, with the value set to "Yes".

• There are no error logs or failed job records related to the recovery recipe.

It seems like the recovery recipe is never invoked, even though all conditions are met.

Has anyone else encountered this issue while using the AOF package from Workato Academy? Any advice would be appreciated!

Thanks in advance.Image -1Image -2Image -3Image -4

[Patel0786 · Accepted solution]

Hi everyone,

I’d like to update that the issue I faced with the AOF Job Recovery recipe not triggering properly has been successfully resolved.

---

✅ Root Cause
The main problem was within the Job Recovery recipe logic. Although the recipe was being called, it was not iterating or retrying as expected due to missing conditional handling and iteration logic.

---

🔧 Solution Implemented
To address this, I introduced the following enhancements using RecipeOps:

• Added a WHILE loop to handle multiple recovery attempts (up to 5 retries)

• Introduced a 60-second wait interval between each retry attempt

• Defined and used conditional variables (Job_ID, Rerun_Time) to monitor and control each rerun cycle

• Used Search job history of specified recipe and Rerun specified jobs actions inside the loop

This structure now ensures that the Job Recovery recipe retries failed jobs consistently within a defined timeframe.

---

📸 Screenshots for Reference

Screenshot 1: Job logs showing 6 successful executions, confirming that the recipe retried and succeeded based on the new logic
Screenshot - 2 (Job Recovery Recipe)Scrrenshot - 3 (UDC Recipe - WFR)nt: Screenshot 2025-05-26 121357.png)

Screenshot 2: Logic implementation inside the WHILE loop within the Job Recovery recipe

Screenshot 3: From the functional UDC recipe, showing that I repeated the job 6 times successfully using AOF logic

---

Let me know if anyone needs help implementing similar retry logic in their AOF setup!

Thanks,

Manish Patel