Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/server-route-params-parse-failure
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

fix(start): handle params.parse failures before server route handlers Since #8434, server route handlers receive parsed params, but a params.parse failure escaped the handler pipeline. A thrown notFound() became a 500, and a page route whose handler would have deferred to rendering could no longer render its not-found page. A thrown notFound() from a handler or from params.parse now responds 404 unless middleware handles it. When params.parse throws on a route with a component and the request explicitly accepts text/html, the handler is skipped and the app router renders the page, as it would without a handler. Refs #8431 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3

Succeeded

read access token used

d752d1698637

6%

Cache hits

26 of 442 tasks used cache.

74%

Distribution saved time

25m 20s instead of 1h 38m 15s.

Atomizer enabled

169 groups of tasks optimized.

Resource usage is collected per agent

Run-level metrics are not available for distributed runs. View CPU and memory in this CI pipeline execution’s Analysis page.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

routerWorkspace