Skip to content

Troubleshooting¶

Common .NET isolated worker problems with direct diagnosis and remediation steps.

flowchart TD
    A[Configuration] --> B[Build]
    B --> C[Deploy]
    C --> D[Observe]

Topic/Command Groups¶

Function not discovered after deploy¶

Confirm FUNCTIONS_WORKER_RUNTIME=dotnet-isolated.
Check startup exceptions in log stream.
On Linux Consumption, az functionapp log tail can fail because scm/Kudu endpoints are not available; use Application Insights queries instead.

az functionapp log tail --name "$APP_NAME" --resource-group "$RG"

CLI element	Explanation
Command(s)	`az functionapp log tail`
Key flags	`--name`, `--resource-group`
Variables	`$APP_NAME`, `$RG`
Expected result	Azure CLI completes successfully and returns JSON, table, or no output depending on the command; verify the next documented check before continuing.

Startup failure due to package mismatch¶

Align worker SDK and extension package versions.
Rebuild and republish with clean output.

dotnet clean
dotnet build --configuration Release
dotnet publish --configuration Release --output ./publish
func azure functionapp publish "$APP_NAME"

HTTP 500 from serialization¶

Validate request body parsing and response encoding.
Ensure HttpResponseData is returned on all code paths.

See Also¶

Sources¶