Push-OutputBinding not working in ActivityTrigger

[kwill-MSFT]

Using the standard VSCode function creation templates, I created an orchestrator with an activity function defined as:

function.json

{
    "bindings": [{
            "name": "name",
            "type": "activityTrigger",
            "direction": "in"
        },
        {
            "type": "queue",
            "direction": "out",
            "name": "outputQueueItem",
            "queueName": "outqueue",
            "connection": "AzureWebJobsStorage"
        }
    ]
}

run.ps1

param($name)

Write-Information "Pushing to outputQueueItem output binding"
Push-OutputBinding -Name outputQueueItem -Value "Queue item from Hello1"
Write-Information "Done"

"Hello $name!"

The Write-Information lines get logged, but no queue item is created. The same Push-OutputBinding works fine from other triggers such as an httpTrigger.

Repro attached.

• Queue item gets generated correctly when running http://localhost:7071/api/HttpTrigger1
• Queue item is not generated when running http://localhost:7071/api/orchestrators/DurableFunctionsOrchestrator1

FunctionsOutputBinding.zip

[stefs987]

Just ran into the same issue. It also does not work with a queue as an output binding in an orchestrator and using Push-OutputBinding in the orchestrator. No errors, but queue message is not created. I could also replicate with an activity function as reported by the OP. Any news on this?

[NikoMix]

Also affected by this. There is no Error/Warning/Message showing up, the Queue Item simply does not show up. Application Insights also tracks no calls towards the Storage Account. It's added to Sprint 105 which is showing 3 Months past due - is this still under investigation? Any further information needed?

[haripraghash]

Is this issue sorted? I seem to be having the same issue with the same repro attached above.
I am using an actual storage account as opposed to azurite.

Azure Functions Core Tools
Core Tools Version: 4.0.3971 Commit hash: d0775d487c93ebd49e9c1166d5c3c01f3c76eaaf (64-bit)
Function Runtime Version: 4.0.1.16815

[davidmrdavid]

Hi @haripraghash, @NikoMix, @stefs987, and @kwill-MSFT.

Sorry for the poor communication here, I didn't realize the issue auto-closed when I merged my PR, that was a mistake on my part. This issue was patched in PR #702 and will be included as a part of the next PowerShell Azure Functions worker release. Unfortunately, I don't have much control over the speed of that process, but I understand it takes a few weeks.

For context about the future: I've taken ownership of the Durable Functions PowerShell experience, and I'm working to improve various other parts of it. In particular, with respect to the speed at which these patches can be released, I'm looking to make the Durable Functions component of the PowerShell worker be independently released, which would give me more control over the release cycle and speed; a similar model to what we have in the JS and Python experiences for Durable Functions. In any case, I wanted to give a heads up that further improvements are in the works, but it'll require a few months to get there.