Azure / Azure/static-web-apps

Integrated SWA Functions reports unhealthy AzureWebJobsStorage, but setting is blocked in SWA config

Open
#1,728 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
346
Forks
67
PR merge metrics
No merged PRs in 30d

Description

We see recurring health telemetry in Application Insights:

Message [Tag=''] Process reporting unhealthy: Unhealthy. Health check entries are {"azure.functions.web_host.lifecycle":{"status":"Healthy","description":null},"azure.functions.script_host.lifecycle":{"status":"Healthy","description":null},"azure.functions.webjobs.storage":{"status":"Unhealthy","description":"**Unable to create client for AzureWebJobsStorage**"}}
Category Microsoft.Azure.WebJobs.Script.Diagnostics.HealthChecks.TelemetryHealthCheckPublisher

In integrated Static Web Apps API, adding app setting `AzureWebJobsStorage` is rejected:
_InvalidAppSettings: AppSetting with name(s) 'AzureWebJobsStorage' are not allowed._

So users cannot fix the runtime health check even though the app works (functions execute, Table output works via custom connection setting, alerts fire).

Expected:
- Either SWA should internally provide/configure `AzureWebJobsStorage` for integrated Functions, OR
- suppress this health check in integrated SWA mode, OR
- provide a documented supported alternative.

Actual:
- Persistent unhealthy health check noise in App Insights, no supported config path.

Repro:
1) Create SWA with integrated Functions API (.NET isolated).
2) Configure custom binding connection (works).
3) Observe App Insights health check telemetry for `AzureWebJobsStorage`.
4) Try adding `AzureWebJobsStorage` in SWA app settings -> rejected as invalid.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.