Skip to content

Troubleshooting

This runbook-style reference captures common Node.js v4 issues with practical checks and resolutions.

Topic/Command Groups

flowchart TD
    A[Issue] --> B[Evidence]
    B --> C[Diagnosis]
    C --> D[Fix]

Functions not discovered

  • Confirm FUNCTIONS_WORKER_RUNTIME=node.
  • Check startup logs for module resolution errors.
az functionapp log tail --name $APP_NAME --resource-group $RG

Runtime version mismatch

  • Validate runtime and Node settings.
  • For Linux apps, validate siteConfig.linuxFxVersion in addition to app settings.
az functionapp config appsettings list --name $APP_NAME --resource-group $RG --query "[?name=='WEBSITE_NODE_DEFAULT_VERSION' || name=='FUNCTIONS_EXTENSION_VERSION']"
az functionapp config show --name $APP_NAME --resource-group $RG --query "linuxFxVersion"

Out-of-memory under load

  • Set languageWorkers__node__arguments=--max-old-space-size=4096.
  • Reduce dependency footprint and stream large payloads.

Trigger binding failures

  • Check AzureWebJobsStorage and related connection settings.
  • Validate queue or blob names and identity permissions.

See Also

Sources