Set-DurableCustomStatus doesn't exist on Azure Functions PaaS

[TheGreggle]

Attempting to call Set-DurableCustomStatus as per the example here on Azure PaaS.

On Azure PaaS, the error The term 'Set-DurableCustomStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. occurs. The same issue was posted here

In Azure, FUNCTIONS_WORKER_RUNTIME is set to powershell. FUNCTIONS_EXTENSION_VERSION is set to ~3. PowerShell Core Version is 7.0.

The PowerShell Worker code was updated here #592 to support Set-DurableCustomStatus.

Locally, downloaded version 3.0.15584 and replaced the worker files in "C:\Program Files\Microsoft\Azure Functions Core Tools\workers\powershell". After this, Set-DurableCustomStatus works locally.

Is there a way to update Azure Functions PaaS to support the new code and Set-DurableCustomStatus?
If not, is there an ETA on when this may be available (preview or GA)?

Thanks

[AnatoliB]

@TheGreggle To use this feature, you need Functions runtime 3.0.15584 or higher, and it may not be rolled out to your region yet. Please restart your app and check the version under Overview/Essentials in the Portal (you may need to wait for a few seconds for it to appear):

If you see anything lower than 3.0.15584, please wait for a few days. If you see 3.0.15584 or higher, and Set-DurableCustomStatus is still not recognized, please let us know.

[TheGreggle]

@AnatoliB thanks for your quick response.

I didn't know that Runtime version was there. Very handy.

My function version is 3.0.15584.0 and in the Australia East region.
Is there anything else I can run to give you some more information?

[AnatoliB]

@TheGreggle I was unable to reproduce the issue on 3.0.15584. If this still happens for you, could you please point us to the invocation logs by using these instructions? Could you please also share the entire source code of your orchestrator function?

[TheGreggle]

@AnatoliB thanks again for your assistance. To be sure, and so I could send you a clean example, I deployed the unmodified example and it worked.

I then re-deployed my version (which was failing) and it worked. I think I was just unlucky, and version 3.0.15584 must have deployed whilst I was writing this up.

At least you taught me how to check the runtime version. Once again thank you for your help.

[AnatoliB]

Closing for now, please let us know if it happens again