[Incident][108dev] Intermittent 500 on essays endpoints from SWA frontend

Open
#141 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, python
Domain
api, cloud, devops

Research direction

Start with the three APIM entry points, /api/essays/resources, /api/essays/essays, and /api/essays/assemblies, and review the live remediation and drift context in issue #139. Inspect the IaC and workflow areas for runtime protections, then define synthetic checks from the SWA origin and correlate failures with deployments; done means intermittent failures are detectable and environment resets are prevented.

Written by the indexing model from the issue text.

Description

Summary

A new frontend incident was observed during live demo prep: essays screen failed with 500 responses on APIM routes.

Observed from browser console (SWA):

  • GET /api/essays/resources -> 500
  • GET /api/essays/essays -> 500
  • GET /api/essays/assemblies -> 500

Scope

  • Environment: 108dev
  • Source: SWA frontend (
    ice-flower-0be65ed0f.1.azurestaticapps.net)
  • Impact: Essays page displays no available cases and cannot load data.

Verification done now

Re-check from command line against same APIM routes:

  • Preflight CORS for all three routes -> 200 with Access-Control-Allow-Origin set to SWA origin.
  • Functional GET for all three routes -> 200 with payload.

This indicates an intermittent live regression window (transient backend/runtime drift or in-flight deployment state), not a persistent outage at check time.

Actions tracked

  • Live remediation actions and drift context are tracked in #139.
  • This issue is opened to track intermittent essays endpoint instability specifically.

Next steps

  • Add periodic synthetic checks for /api/essays/resources|essays|assemblies from SWA origin.
  • Backport runtime drift protections to IaC/workflow to prevent env resets.
  • Correlate failures with active workflow/deploy windows and revision rollouts.

Related: #139

Dominant language
Python
Stars
17
Forks
8
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure-Samples/tutor

All issues in Azure-Samples/tutor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.