Skip to content

MCP enterprise-managed authorization (client) #4860

MCP enterprise-managed authorization (client)

MCP enterprise-managed authorization (client) #4860

Re-run triggered August 26, 2026 21:41
Status Failure
Total duration 3m 30s
Artifacts –

ci.yml

on: pull_request
Changed paths
7s
Changed paths
Matrix: e2e
Cloud evaluated closure
49s
Cloud evaluated closure
Desktop smoke build
53s
Desktop smoke build
Self-host Docker image
1m 10s
Self-host Docker image
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
E2E (cloud 14of16)
Process completed with exit code 1.
[cloud] scenarios/graphql-introspection-health.test.ts > GraphQL · failed introspection blocks connection creation with an actionable error: e2e/scenarios/graphql-introspection-health.test.ts#L81
AssertionError: expected 'The endpoint rejected the credential …' to contain 'The endpoint rejected the credential …' Expected: "The endpoint rejected the credential with HTTP 401." Received: "The endpoint rejected the credential with HTTP 403. Check the credential and selected authentication method. Upstream said: API rate limit exceeded for your request. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)" ❯ scenarios/graphql-introspection-health.test.ts:81:27 ❯ step src/surfaces/browser.ts:276:15 ❯ scenarios/graphql-introspection-health.test.ts:71:9 ❯ src/surfaces/browser.ts:288:13
E2E (cloud 10of16)
Process completed with exit code 1.
[cloud] cloud/mcp-browser-resume-page.test.ts > MCP approval · browser resume page approves a paused execution through the UI: e2e/cloud/mcp-browser-resume-page.test.ts#L250
TimeoutError: locator.waitFor: Timeout 30000ms exceeded. Call log: - waiting for getByText('Approve sent') to be visible ❯ cloud/mcp-browser-resume-page.test.ts:250:54 ❯ step src/surfaces/browser.ts:276:15 ❯ cloud/mcp-browser-resume-page.test.ts:248:15 ❯ src/surfaces/browser.ts:288:13
E2E (cloud 14of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 7of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
E2E (cloud 10of16)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/