Sub orchestrator output returns null

[azure]

Sub orchestrator output returns null

[kashimiz]

Glad to hear the workaround is working! I'll close this and keep the other issue open to track the bug.

[kashimiz]

Hi @eirikb, thanks for reporting this issue. It looks like this bug has the same cause as #54, namely that not specifying an instanceId in the callSubOrchestrator call is confusing the module's history replay.

As a workaround, please call callSubOrchestrator with all arguments explicitly defined for now:

callSubOrchestrator(name: string, input?: unknown, instanceId?: string)

[eirikb]

Hi

I've tested this now, and it does indeed work when I pass in all arguments. Did the same as @hanvyj, and this works fine:

return yield context.df.callSubOrchestrator('Orchestrator2', null, `${context.df.instanceId}:0`);

I guess this can be closed, or held open until default arguments works?