GitHub Actions deployment to Azure Static Web Apps succeeds but shows stale build content

I have a Static Web App connected to a GitHub repository via the auto-generated GitHub Actions workflow. The deployment step in the Actions log completes successfully every time (green checkmark, no errors), and the workflow correctly reports the build and deploy jobs as finished.

However, when I visit the live Azure-generated URL, it sometimes serves an older version of the site, not the version from the most recent commit. Hard-refreshing the browser and even testing in an incognito window doesn't fix it, which rules out local browser caching.

What I've checked so far:

• The GitHub Actions run logs show the correct commit hash being built and deployed
• The output_location and app_location in the workflow YAML match my project's actual build output folder
• There's no custom CDN or Cloudflare proxy in front of the Azure URL, this is the raw *.azurestaticapps.net domain
• Waiting 10-15 minutes after deployment doesn't resolve it consistently, sometimes it updates immediately, sometimes it takes much longer

Is this a known caching layer on Azure's edge/CDN side for Static Web Apps that isn't documented, or could this be related to how the Oryx build step handles cached dependencies? Any guidance on how to force a clean rebuild or verify what's actually being served on Azure's end (versus what GitHub Actions reports as deployed) would be appreciated.