Failed to load the playwright workspace test run details

Question

I've created a playwright workspace, correclty set up the permissions and the repository.The test runs appear on the list but once I try to open one it tells meHTTP 404: The specified container does not exist. For troubleshooting guidance, visit troubleshooting guide.

Answer 1

 Hello Francesco Borrelli,

Thank you for reaching out to the Microsoft Q&A forum.

Playwright Workspaces stores test artifacts (reports, traces, videos) in a corresponding blob container inside the workspace’s associated Storage Account. But a test run appears in the UI even if storage upload fails, so you only notice a problem when opening the run.

Common triggers (from Microsoft docs & Q&A):

1. Storage account or container is missing

— Deleted manually — Incorrect name — Not created by the service

2. Workspace does not have permission

You must have at least Storage Blob Data Contributor on the storage account.

3. Reporter not configured (the Azure Service Reporter is required)

If playwright.service.config.ts isn’t configured properly, artifacts do not upload.

4. Misalignment between workspace region and storage location

Playwright reporting uses the workspace region to place containers.

 

How to Fix It (exact steps)

1. Verify the Workspace's Storage Account Exists

In Azure Portal:

Your Playwright Workspace → Properties → Storage Account

Check:

• Does the storage account still exist?
• Does it contain a container with a name like:

playwrightartifacts

playwright-testresults

If missing → the workspace cannot create it automatically without correct permissions.

2. Ensure you have correct permissions

You must have:

• Contributor (or Owner) on the Workspace
• Storage Blob Data Contributor on the Storage Account

Without this role, artifacts are never uploaded → container appears “missing”.

3. Re-check your Playwright Reporter Configuration

From the docs:

• playwright.service.config.ts must include the Azure service reporter
• The workspace endpoint must be exported via:

PLAYWRIGHT_SERVICE_URL=<workspace-region-endpoint>

If not configured, no artifact upload occurs → Azure shows 404.

4. Run a fresh test after fixing configs

Because old runs with missing containers can never be opened. Only new runs will work once the storage container is properly created.

Direct match to known issue

Your payload:

resourceId: /subscriptions/.../Microsoft.LoadTestService/playwrightworkspaces/CEP-MySignins-E2E

code: 404

The identical case appears in: “Failed to load the playwright workspace test run details”

The Microsoft response states:

Problem = Storage container missing Fix = Ensure storage account exists + correct permissions + reporter configuration

 

What you should do next

To solve it immediately:

Step A: Open your Workspace → Check linked Storage Account

Step B: Assign yourself:

• Storage Blob Data Contributor on that account

Step C: Re-run a test after confirming:

• playwright.service.config.ts
• PLAYWRIGHT_SERVICE_URL

Step D: Try opening the new run (old runs remain broken) 

Need me to check your configuration?

If you want, paste your:

• playwright.config.ts
• playwright.service.config.ts
• The workspace region and storage account name

I can validate the setup and tell you exactly where the gap is.

If the answer was helpful, could you please click "Accept Answer" and "Upvote" and this helps other community members who may encounter a similar issue in the future.

 

Answer 2

The HTTP 404 error indicating that "The specified container does not exist" suggests that there may be an issue with the storage account linked to your Playwright workspace. Here are some potential troubleshooting steps you can take:

1. Check Storage Account Existence: Ensure that the storage account associated with your Playwright workspace exists and has not been deleted.
2. Permissions: Verify that you have the necessary permissions to access the storage account. You should have at least the "Contributor" role assigned to the storage account to view the test artifacts.
3. Configuration: Ensure that the Playwright Workspaces reporter is configured correctly in your test setup. If the reporter is not set up properly, it may lead to issues with accessing the test run details.
4. Container Name: Double-check the container name in your configuration to ensure it matches the one in the Azure portal.

If you continue to experience issues, consider consulting the troubleshooting guide for further assistance.

---

References:

• Troubleshoot issues with Playwright Workspaces reporting
• Troubleshoot issues with running tests with Microsoft Playwright Testing preview