RuntimeError: function 'func-name' without a $return binding returned a non-None value.

[thec0dewriter]

🐛 Describe the bug
For a few days I keep getting in deployment the following error:

Message: Activity function 'func-name' failed: RuntimeError: function 'func-name' without a $return binding returned a non-None value {"$type":"System.Exception, System.Private.CoreLib","ClassName":"System.Exception","Message":" RuntimeError: function 'func-name' without a $return binding returned a non-None value",

After redeployment the function works for some time then the issue reappears.

🤔 Expected behavior

What should have happened?

I've seen this fix and the error might make sense.
However the error doesn't appear in a local setup, just in deployment.
After the execution error the orchestration is staying in a running state.

The template activity function generated by VS Code has also return statement without any kind of return output binding defined so this is also a bit confusing.

☕ Steps to reproduce

What Durable Functions patterns are you using, if any?
Just sequential function chaining.

Are you running this locally or on Azure?
The problems only appear on azure.

⚡If deployed to Azure

We have access to a lot of telemetry that can help with investigations. Please provide as much of the following information as you can to help us investigate!

• Timeframe issue observed: Last few days, attached id-s from 23 and 26 aug.
• Azure region: West Europe
• Orchestration instance ID(s): ca3eca38431f406198dc2551cf9490c2 b47a61f20b5648299ccf3401052500b1, 7c61b2f476d843bcb5b73f0fef30e78f
• Azure storage account name:

[KhaoticMind]

I'm facing this issue as well.
A function that used to work is giving me this error, and if I try fixing it is just make things worse (keeps throwing errors at different points, even complaining that the activity parameter (a str) should be a httpRequest...

I think the endpoint that is answering these requests is treating the activity call as a http endpoint call and messing things around.

[davidmrdavid]

@thec0dewriter, @KhaoticMind:

Thanks for your report. I have received a few of these over the past day, and it seems that some automatic upgrade may have caused a regression. I'm actively investigating this, so please subscribe to the following thread for updates: #401

[thec0dewriter]

Hello @davidmrdavid
Thanks for picking it up, let me know if I can help.
Have a great day!

[davidmrdavid]

Closing as the known regression was fixed a few weeks back.