Azure / Azure/azure-cli

webapp webjob triggered list drops actionable 409 response body

Open
#33,824 2 comments 1 reaction 3 assignees Claimed by @a0x1ab View on GitHub
act-observability-squad app-service-general Auto-Assign bug Service Attention Web Apps
Dominant language
Python
Stars
4.6k
Forks
3.5k
Avg merge
3d 2h
Merged PRs (30d)
60

Description

## Describe the bug

`az webapp webjob triggered list` drops the actionable response body returned by Kudu for a `409 Conflict`. The CLI reports only a generic status name, hiding the exact configuration prerequisite that failed.

## Related command

Preconditions:

- Linux App Service app.
- `properties.webJobsEnabled=false` on the `Microsoft.Web/sites/config` resource.
- A valid triggered WebJob deployed under `App_Data/jobs/triggered/AppendLine`.

```powershell
az webapp webjob triggered list `
--name `
--resource-group
```

## Errors

Azure CLI output:

```text
Operation returned an invalid status 'Conflict'
```

Exit code: `1`.

The authenticated Kudu endpoint returns an actionable body for the same operation:

```http
GET https://.scm.azurewebsites.net/api/triggeredwebjobs
HTTP/1.1 409 Conflict
```

```json
{
"error": "The web app is not configured to run the web job. Please enable running web jobs before calling the API."
}
```

## Issue script & Debug output

The package was deployed successfully, and Kudu VFS confirmed these files existed:

```text
site/wwwroot/App_Data/jobs/triggered/AppendLine/message.txt
site/wwwroot/App_Data/jobs/triggered/AppendLine/run.sh
site/wwwroot/App_Data/jobs/triggered/AppendLine/settings.job
site/wwwroot/App_Data/jobs/triggered/AppendLine/WebjobTest.AppendLine.dll
site/wwwroot/App_Data/jobs/triggered/AppendLine/WebjobTest.AppendLine.runtimeconfig.json
```

After setting `properties.webJobsEnabled=true`, the unchanged CLI command succeeded and returned the `AppendLine` job. This isolates the conflict to the disabled WebJobs runtime and confirms the service response body contained the required remediation.

## Expected behavior

Azure CLI should include the service response body in its error output, for example:

```text
The web app is not configured to run WebJobs. Enable webJobsEnabled and retry.
```

At minimum, the original JSON error body should be preserved instead of being reduced to `Conflict`.

## Environment Summary

```text
azure-cli 2.88.0
core 2.88.0
telemetry 1.1.0

Extensions:
azure-devops 1.0.6
kusto 0.5.0
resource-graph 2.1.1

Dependencies:
msal 1.36.0
azure-mgmt-resource 24.0.0

Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Python (Windows) 3.14.5 [MSC v.1944 64 bit (AMD64)]
PowerShell 7.6.4
Windows 10.0.26200
```

## Additional context

The generic CLI output led to unnecessary investigation of deployment layout even though the files were present. Direct Kudu inspection immediately identified the missing site-level runtime switch.

No existing Azure/azure-cli issue containing the exact Kudu error text was found.

Suggested assignee: @seligj95

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.