Getting Orchestrator function failed with OOProc schema V2 in azure durable function app

Question

Getting Orchestrator function failed with OOProc schema V2 in azure durable function app

Nirali Shah 156

We have created azure durable function app. In this, we are getting Orchestrator function failed with OOProc schema V2, expected actions array to be of length 1 in outer layer but got size: 2. Attached screenshot for your reference.

User's image After successful exection of Eternal Orchestrator function the status of execution display Failed though it continue as new and execute again but status is still failed for all the exection. Here, is the code block that we have used to implement eternal orchestration mechanism.

next_check = context.current_utc_datetime + \
        timedelta(minutes=export_schedule_minutes)
yield context.create_timer(next_check)
context.continue_as_new(None)

The function app is running on a Linux Consumption plan. Can anyone suggest the solution for this or any workaround to avoid this error?

Shireesha Eeraboina 3,345 Reputation points Microsoft External Staff Moderator

2025-04-15T05:52:46.0566667+00:00
Hi Nirali Shah,

Thanks for sharing the details and screenshot.

The error you're seeing usually happens when the orchestrator yields more than one action in a single step. With schema V2, Durable Functions expect only one top-level action per orchestration turn.

In your code, it looks like continue_as_new is being called right after yield context.create_timer(...), which can lead to two actions being registered in the same turn.

To fix this, try using:

yield context.create_timer(next_check) return context.continue_as_new(None)

This ensures only one action is processed per turn.

For more info, here are helpful references:

Durable Functions – Orchestrator Code Constraints

Durable orchestrations

Durable Functions Troubleshooting Guide

Let us know if the issue continues after this change. We’re happy to help further!
Shireesha Eeraboina 3,345 Reputation points Microsoft External Staff Moderator

2025-04-16T04:28:12.08+00:00

Hi Nirali Shah,

Following up to see if you have a chance to check my previous response and helped do let me know if you have any further questions on this.
Shireesha Eeraboina 3,345 Reputation points Microsoft External Staff Moderator

2025-04-17T05:09:32.34+00:00

Hello Nirali Shah,

I'm following up to check if you've had a chance to review my previous response. Please feel free to let me know if you have any further questions.
Nirali Shah 156 Reputation points

2025-06-09T13:29:27.6866667+00:00
@Shireesha Eeraboina We've tried the solution suggested by you but it is not working in our case. Instead we've tried the solution as below:

yield context.create_timer(next_check) yield context.continue_as_new(None)

This solution works for us for some of the case, however in one of the orchestrator where we're calling multiple activities and sub orchestrators, we're able to resolve this issue but getting a new error related to OOProc schema V2.

I've attached the Screenshot of the error for your reference.

Can you please help us to understand the issue and any solution for this?
Praveen Kumar Gudipudi 1,085 Reputation points Microsoft External Staff Moderator

2025-06-12T04:20:53.6733333+00:00

Hello Nirali Shah,

Your using

yield context.create_timer(next_check)

yield context.continue_as_new(None)

So, please use

yield context.create_timer(next_check)

return context.continue_as_new(None) and let us know with an update.

This error indicates that the orchestrator function is yielding more than one action, which is not allowed under the OOProc schema V2. Specifically, when using schema V2, the Durable Functions framework expects only one top-level action to be processed per orchestration turn.

If your orchestration code tries to yield more than one action (like calling continue_as_new or multiple timers) in a single step, you will encounter this error.

This ensures that only one action is processed per turn, preventing the error.

Your answer

Shireesha Eeraboina 3,345 Reputation points Microsoft External Staff Moderator

2025-04-15T05:52:46.0566667+00:00

Hi Nirali Shah,

Thanks for sharing the details and screenshot.

The error you're seeing usually happens when the orchestrator yields more than one action in a single step. With schema V2, Durable Functions expect only one top-level action per orchestration turn.

In your code, it looks like continue_as_new is being called right after yield context.create_timer(...), which can lead to two actions being registered in the same turn.

To fix this, try using:

yield context.create_timer(next_check) return context.continue_as_new(None)

This ensures only one action is processed per turn.

For more info, here are helpful references:

Durable Functions – Orchestrator Code Constraints

Durable orchestrations

Durable Functions Troubleshooting Guide

Let us know if the issue continues after this change. We’re happy to help further!
Shireesha Eeraboina 3,345 Reputation points Microsoft External Staff Moderator

2025-04-16T04:28:12.08+00:00

Hi Nirali Shah,

Following up to see if you have a chance to check my previous response and helped do let me know if you have any further questions on this.
Shireesha Eeraboina 3,345 Reputation points Microsoft External Staff Moderator

2025-04-17T05:09:32.34+00:00

Hello Nirali Shah,

I'm following up to check if you've had a chance to review my previous response. Please feel free to let me know if you have any further questions.
Nirali Shah 156 Reputation points

2025-06-09T13:29:27.6866667+00:00

@Shireesha Eeraboina We've tried the solution suggested by you but it is not working in our case. Instead we've tried the solution as below:

yield context.create_timer(next_check) yield context.continue_as_new(None)

This solution works for us for some of the case, however in one of the orchestrator where we're calling multiple activities and sub orchestrators, we're able to resolve this issue but getting a new error related to OOProc schema V2.

I've attached the Screenshot of the error for your reference.

Can you please help us to understand the issue and any solution for this?
Praveen Kumar Gudipudi 1,085 Reputation points Microsoft External Staff Moderator

2025-06-12T04:20:53.6733333+00:00

Hello Nirali Shah,

Your using

yield context.create_timer(next_check)

yield context.continue_as_new(None)

So, please use

yield context.create_timer(next_check)

return context.continue_as_new(None) and let us know with an update.

This error indicates that the orchestrator function is yielding more than one action, which is not allowed under the OOProc schema V2. Specifically, when using schema V2, the Durable Functions framework expects only one top-level action to be processed per orchestration turn.

If your orchestration code tries to yield more than one action (like calling continue_as_new or multiple timers) in a single step, you will encounter this error.

This ensures that only one action is processed per turn, preventing the error.

Share via

Getting Orchestrator function failed with OOProc schema V2 in azure durable function app

Your answer