Skip to content

azure_functions_worker logging shows wrong programming model #479

@danielniccoli

Description

@danielniccoli

🐛 Describe the bug

A clear and concise description of what the bug is.

The standard logs from the azure_functions_worker show the wrong programming model. I'm using the V2 model, but the logs show the V1 model.

Below logs are the output when calling an activity (v2):

[2024-01-22T11:55:37.354Z] INFO - 2024-01-22 12:55:37,340 - azure_functions_worker - dispatcher - Received WorkerLoadRequest, request ID 104b2e12-a1f7-4ec6-ab02-8c58adb58a33, function_id: 5cc28705-7f75-56c8-9b61-62f99a7bc9a7,function_name: validate_owner,      
[2024-01-22T11:55:37.355Z] INFO - 2024-01-22 12:55:37,341 - azure_functions_worker - dispatcher - Successfully processed FunctionLoadRequest, request ID: 104b2e12-a1f7-4ec6-ab02-8c58adb58a33, function ID: 5cc28705-7f75-56c8-9b61-62f99a7bc9a7,function Name: validate_owner,programming model: V1

🤔 Expected behavior

What should have happened?

It should print programming model: V2

Steps to reproduce

What Durable Functions patterns are you using, if any?
Any minimal reproducer we can use?
Are you running this locally or on Azure?

Call an activity in a V2 model durable function on a local functions host.

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!

Not tested

If you don't want to share your Function App or storage account name GitHub, please at least share the orchestration instance ID. Otherwise it's extremely difficult to look up information.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Priority 2bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions