Diagnostics and remediation#

Pulse 1.0.0-beta.1 treats the 114 codes on this page as the stable public CLI diagnostic catalog. Code, category, summary, remediation intent, exit class, and anchor are generated from the same source used by the CLI. Human wording may improve compatibly.

Every catalogued failure links to a versioned installed artifact under:

https://pulsecompute.io/v1.0.0-beta.1/reference/diagnostics/

Uncatalogued/internal or forward-compatible codes link to that reference root instead of inventing a nonexistent anchor. Internal PULSEWASM_* proof/compiler tokens are not part of this public catalog.

Source-form eligibility, trusted awaits, ctx.parallel static shape, Router terminal transfer, and body ownership are centralized in Managed handler TypeScript and JavaScript. Four-mode target claims are centralized in Provider and target compatibility. A Native eligibility diagnostic never authorizes automatic JavaScript fallback.

JSON failure envelope#

{
  "status": "error",
  "version": "1.0.0-beta.1",
  "error": {
    "name": "PulseProjectError",
    "code": "PULSE_BUILD_OUT_UNSAFE",
    "title": "Build Out Unsafe",
    "summary": "The resolved build output can escape or alias outside the project root.",
    "category": "safety",
    "message": "Pulse build output must be a child directory of the project root.",
    "remediation": [
      "Choose an output directory that is a real child of the project root."
    ],
    "stability": "preview-stable",
    "scope": "public",
    "docs": "https://pulsecompute.io/v1.0.0-beta.1/reference/diagnostics/#pulse-build-out-unsafe"
  }
}

Configured secret values are redacted before diagnostics are serialized.

Fastly local execution boundary#

Pulse executes generated bin/main.wasm through an inspected local Compute launcher. PULSE_FASTLY_BIN selects CLI-owned fastly compute serve --file; PULSE_VICEROY_BIN selects direct viceroy serve when no explicit Fastly CLI launcher is selected. External Fastly execution remains an explicit environment-dependent gate.

Exit codes#

Development HTTP responses#

When a diagnostic is converted into a response by pulse dev, an explicitly catalogued HTTP status takes precedence. Catalogued codes without an explicit HTTP mapping use 500 as a fail-closed development-server fallback. CLI exit codes remain independent from HTTP status.

Executable schema failure example#

The documented schema project includes an intentionally invalid case:

pulse test examples/02-request-schema --case invalid-user --json

{
  "status": "passed",
  "cases": [
    {
      "name": "invalid-user",
      "status": "passed",
      "expectedError": {
        "code": "PULSE_SCHEMA_DECODE",
        "category": "request",
        "docs": "https://pulsecompute.io/v1.0.0-beta.1/reference/diagnostics/#pulse-schema-decode"
      }
    }
  ]
}

Complete public catalog#

Usage diagnostics#

PULSE_COMMAND_UNKNOWN — Command Unknown#

The requested pulse command is not part of the supported CLI.

• Category: usage
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI reference

Remediation

1. Run pulse --help and choose one of the documented commands.

PULSE_ARGUMENT_MISSING — Argument Missing#

A command-line option that requires a value was supplied without one.

• Category: usage
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI reference

Remediation

1. Provide the missing flag value and rerun the command.
2. Run pulse --help for the command signature.

PULSE_ARGUMENT_UNEXPECTED — Argument Unexpected#

The command received an option or positional argument it does not accept.

• Category: usage
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI reference

Remediation

1. Remove the unsupported argument or use the documented flag.
2. Run pulse --help for the command signature.

PULSE_PROVIDER_FLAG_REMOVED — Provider Flag Removed#

Provider selection is project configuration, not a command-line override.

• Category: usage
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI reference

Remediation

1. Select host and target in a .pulse/config.ts profile.
2. Use pulse compile for provider-neutral Wasm or pulse build for the configured deployment target.

PULSE_SOURCE_ONLY_REMOVED — Source Only Removed#

The former source-only JavaScript packaging mode is no longer part of native builds.

• Category: usage
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI reference

Remediation

1. Run pulse build; native builds emit generated source and provider Wasm together.

Project diagnostics#

PULSE_CONFIG_NOT_FOUND — Config Not Found#

Project discovery did not find an explicit Pulse configuration file.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Run pulse init to create .pulse/config.ts.
2. Ensure the command runs inside the intended project directory.

PULSE_PROFILE_SELECTION_REQUIRED — Profile Selection Required#

No project profile was selected by CLI, environment, or default configuration.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Pass --profile, set PULSE_PROFILE, or configure pulse.defaultProfile.

PULSE_PROFILE_UNKNOWN — Profile Unknown#

The selected profile is absent from the project declaration.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Select one of the profiles declared next to the reserved pulse object.

PULSE_CONFIG_PLAN_PARITY_FAILED — Config Plan Parity Failed#

Static and runtime configuration normalization produced different canonical plans.

• Category: project
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Keep the config factory within the sealed static grammar and report the divergent plan hashes.

PULSE_JAVASCRIPT_APPLICATION_PLAN_INVALID — Javascript Application Plan Invalid#

The JavaScript loader received a value outside the normalized application-plan contract.

• Category: project
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Rebuild the JavaScript application plan from the configured entry and sealed reachable graph.

PULSE_JAVASCRIPT_APPLICATION_ENTRY_INVALID — Javascript Application Entry Invalid#

The JavaScript plan entry is not a project-owned application module.

• Category: project
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Default-export a Router, Pulse application, or managed handler from a project-owned entry module.

PULSE_JAVASCRIPT_APPLICATION_EXPORT_INVALID — Javascript Application Export Invalid#

The JavaScript entry does not export a managed Pulse application.

• Category: project
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Default-export a Router, Pulse application, or managed handler.

PULSE_JAVASCRIPT_MODULE_NOT_FOUND — Javascript Module Not Found#

A graph-owned project module is absent at JavaScript load time.

• Category: project
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Restore the graph-owned project module or rebuild the plan after the source change.

PULSE_RUNTIME_APPLICATION_EXPORT_INVALID — Runtime Application Export Invalid#

The application value is not a Router, Pulse application, or managed handler.

• Category: project
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Default-export a Router, Pulse application, or managed handler.

PULSE_CONFIG_LOAD_FAILED — Config Load Failed#

The selected project configuration threw or failed while being loaded.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Fix the config import or runtime error.
2. Use pulse doctor --json to inspect the underlying cause.

PULSE_ENTRY_NOT_FOUND — Entry Not Found#

The configured canonical handler entry file does not exist.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Create the configured entry file or correct pulse.entry in .pulse/config.ts.

PULSE_PROJECT_ROOT_MISSING — Project Root Missing#

The selected project directory does not exist.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Create or correct the positional project directory.

PULSE_INIT_NOT_EMPTY — Init Not Empty#

Project initialization would write into a non-empty directory without explicit force.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Choose an empty directory or pass --force only when overwriting is intentional.

PULSE_INIT_FILE_EXISTS — Init File Exists#

Project initialization would replace an existing file that is not safe to overwrite.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Remove the conflicting file or choose another target directory.

PULSE_CONFIG_IMPLICIT — Config Implicit#

A command is relying on an implicit project shape instead of an explicit configuration.

• Category: project
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project configuration

Remediation

1. Run pulse init or create .pulse/config.ts to make workspace ownership explicit.

Test diagnostics#

PULSE_TEST_HARNESS_NOT_FOUND — Test Harness Not Found#

The configured workspace-relative test harness does not exist.

• Category: test
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI test behavior

Remediation

1. Create the workspace-relative file configured by pulse.tests.

PULSE_TEST_HARNESS_EXPORT_INVALID — Test Harness Export Invalid#

The configured harness does not export the required ordered case collection.

• Category: test
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI test behavior

Remediation

1. Export an ordered case array or an object containing a cases array.

PULSE_TEST_EXPECT_INVALID — Test Expect Invalid#

A project test case uses an invalid expectation shape for its HTTP or event discriminant.

• Category: test
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI test behavior

Remediation

1. Use the documented expectation shape for the selected HTTP or event case.
2. Event emitted-frame expectations must be ordered arrays of canonical frames.

PULSE_TEST_EVENT_INVALID — Test Event Invalid#

A discriminated event test case is missing or violates the canonical bounded event-frame shape.

• Category: test
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI test behavior

Remediation

1. Use a discriminated kind: "event" case with one bounded type, schema or schemaId, and schema-dependent payload.
2. Inspect the event catalog with pulse inspect --json.

Capability diagnostics#

PULSE_TARGET_IMPLEMENTATION_PENDING — Target Implementation Pending#

The selected execution target is explicit but not implemented for this command.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select a native profile for build, test, or dev.
2. Use inspect or doctor to retain the JavaScript selection without fallback.

PULSE_JAVASCRIPT_APPLICATION_UNAVAILABLE — Javascript Application Unavailable#

The selected JavaScript application has one or more explicit target blockers.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Inspect the application-plan blockers and select only explicitly realized package and provider capabilities.
2. Pulse will not fall back to native or another target automatically.

PULSE_JAVASCRIPT_PACKAGE_REALIZATION_UNAVAILABLE — Javascript Package Realization Unavailable#

A reachable Pulse-aware package has no JavaScript realization for the selected target.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Use a package with an explicit JavaScript realization or select a native target.
2. Inspect package target support with pulse inspect --json.

PULSE_PACKAGE_JAVASCRIPT_REALIZATION_NOT_IMPLEMENTED — Package Javascript Realization Not Implemented#

A reachable Pulse-aware package explicitly declares that its JavaScript realization is not implemented.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select the native target for this package or wait for its declared JavaScript realization.
2. No automatic fallback occurs.

PULSE_JAVASCRIPT_PACKAGE_ESM_UNSUPPORTED — Javascript Package Esm Unsupported#

The current graph-backed Node loader cannot require the selected ESM-only package entry.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Use a CommonJS-compatible package entry for the current Node loader or defer the package to a later JavaScript bundling contract.

PULSE_JAVASCRIPT_PACKAGE_MODULE_UNAVAILABLE — Javascript Package Module Unavailable#

The graph-selected JavaScript package module cannot be loaded from the application workspace.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Install the exact package selected by the reachable graph in the application workspace.

PULSE_JAVASCRIPT_EXTERNAL_MODULE_UNAVAILABLE — Javascript External Module Unavailable#

A declared external module is unavailable to the JavaScript application loader.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Install or explicitly declare the external module required by the JavaScript target.

PULSE_EXPERIMENTAL_NATIVE_SIZE_UNSUPPORTED — Experimental Native Size Unsupported#

The experimental Native size optimizer cannot be used for a JavaScript build target.

• Category: capability
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select a profile with target: "native" or use pulse compile.
2. Remove --experimental-native-size for JavaScript build output.

PULSE_PROVIDER_COMPILE_ONLY — Provider Compile Only#

The none provider cannot execute development-server or project-test behavior.

• Category: capability
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select an executable provider before running pulse dev or pulse test.

PULSE_TEST_PROVIDER_REQUIRED — Test Provider Required#

Project tests require an executable provider.

• Category: capability
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select an executable provider for pulse test.

PULSE_DEV_PROVIDER_UNSUPPORTED — Dev Provider Unsupported#

The development server requires an executable provider.

• Category: capability
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select an executable provider for pulse dev.

PULSE_PROVIDER_CAPABILITY_MISSING — Provider Capability Missing#

The selected provider lacks a binding required by the compiled application.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 501
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Configure the required provider binding or select a provider that implements the capability.
2. Run pulse inspect --json to view required capabilities and bindings.

PULSE_PROVIDER_CAPABILITY_UNSUPPORTED — Provider Capability Unsupported#

The selected provider cannot realize a capability required by the application.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 501
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Remove the unsupported capability or select a compatible provider.

PULSE_EVENT_TARGET_UNSUPPORTED — Event Target Unsupported#

The selected provider target cannot realize or test the reachable event plane.

• Category: capability
• CLI exit class: 3
• Development HTTP status: 501
• Stability/scope: preview-stable / public
• Related reference: Provider restrictions

Remediation

1. Select a target whose descriptor and provider event driver satisfy every reachable event requirement.
2. Use pulse inspect --json to review event target support; Pulse will not select another target automatically.

Compile diagnostics#

PULSE_JAVASCRIPT_APPLICATION_GRAPH_FAILED — Javascript Application Graph Failed#

The sealed reachable graph could not be built for JavaScript application loading.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Fix the first reachable-graph diagnostic before loading the JavaScript application.

PULSE_JAVASCRIPT_IMPORT_NOT_IN_GRAPH — Javascript Import Not In Graph#

Runtime evaluation requested an import absent from the sealed reachable graph.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Keep runtime imports within the sealed reachable graph and avoid evaluation-time dynamic loading.

PULSE_JAVASCRIPT_MODULE_COMPILE_FAILED — Javascript Module Compile Failed#

A graph-owned TypeScript or JavaScript module could not be transpiled for the Node loader.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Fix the TypeScript or JavaScript syntax in the graph-owned project module.

PULSE_HANDLER_ASYNC_REQUIRED — Handler Async Required#

A managed handler in a conventional Pulse project is missing its required async wrapper.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Declare every managed handler, middleware function, and error handler with async.
2. Native lowering erases the wrapper; no Promise runtime or Asyncify support is added.

PULSE_PROJECT_COMPILE_FAILED — Project Compile Failed#

Whole-project compilation failed and contains one or more nested diagnostics.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Read the nested diagnostics and fix the first reported source or schema error.
2. Run pulse inspect --json or pulse doctor --json for structured diagnostics.

PULSE_CANONICAL_COMPILE_FAILED — Canonical Compile Failed#

The handler uses a source form outside the canonical Beta authoring subset.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Rewrite the handler using the documented canonical API subset.
2. Run pulse inspect --json to see unsupported source forms.

PULSE_CANONICAL_NATIVE_PLAN_FAILED — Canonical Native Plan Failed#

The canonical handler could not be represented by the provider-neutral native execution-plan contract.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Inspect the native-plan diagnostics and rewrite unsupported canonical control flow.
2. Run pulse inspect --json to view the provider-neutral plan boundary.

PULSE_CANONICAL_NATIVE_AS_GENERATION_FAILED — Canonical Native As Generation Failed#

The validated native plan could not be rendered into the bounded AssemblyScript state-machine source.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Inspect the generated-native diagnostic and rewrite unsupported canonical expressions.
2. Retain the plan hash and diagnostic detail when reporting a compiler defect.

PULSE_PACKAGE_LOWERING_FAILED — Package Lowering Failed#

A package-owned API call could not be lowered into its canonical effect contract.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Fix the package-owned API call shape reported in the nested diagnostic.
2. Keep package effects in the documented static positions.

PULSE_NATIVE_IMPORT_UNSUPPORTED — Native Import Unsupported#

A reachable runtime import has no trusted Pulse native contract.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Remove or isolate the runtime dependency, use a trusted Pulse capability, or select an explicit JavaScript target when available.
2. Pulse will not change targets automatically.

PULSE_PACKAGE_SUBPATH_UNSUPPORTED — Package Subpath Unsupported#

A Pulse-aware package was imported through a subpath that is not native-lowerable.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Import the package through its documented Pulse lowerable facade, or keep the package behind a JavaScript-only boundary.
2. Run pulse inspect --json to review package ownership and native eligibility.

PULSE_PACKAGE_REEXPORT_LOWERING_DEFERRED — Package Reexport Lowering Deferred#

A package-owned helper is graph-owned but reaches application code through a project re-export whose lowering remains deferred.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Import the package-owned facade directly until helper/re-export lowering is enabled by the package contract.
2. The graph records the owning package; no fallback occurs.

PULSE_APPLICATION_ENTRY_LIFECYCLE_SIDE_EFFECT — Application Entry Lifecycle Side Effect#

The configured application entry graph starts a known provider lifecycle during module evaluation.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Keep the configured application entry import-safe and move provider lifecycle startup to a separate runner.
2. Use the provider lifecycle through CLI delegation rather than starting infrastructure during application import.

PULSE_PACKAGE_BINDING_OWNERSHIP_AMBIGUOUS — Package Binding Ownership Ambiguous#

A project binding or re-export resolves to more than one package-owned symbol.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Remove the ambiguous re-export or give each package-owned helper one unambiguous source owner.

PULSE_PACKAGE_CONTRACT_NOT_RECOGNIZED — Package Contract Not Recognized#

The graph selected a trusted package contract that the package recognizer did not recover from its owning source module.

• Category: compile
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Verify the trusted package manifest and direct facade import, then retain the graph and package diagnostics when reporting the issue.

Internal diagnostics#

PULSE_JAVASCRIPT_PACKAGE_PLAN_MISSING — Javascript Package Plan Missing#

The graph selected a package module that is absent from the JavaScript application plan.

• Category: internal
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Rebuild the JavaScript plan and retain the graph and plan hashes when reporting the inconsistency.

PULSE_JAVASCRIPT_GRAPH_EDGE_AMBIGUOUS — Javascript Graph Edge Ambiguous#

The sealed JavaScript graph contains more than one runtime edge for the same import.

• Category: internal
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Retain the graph manifest and report the duplicate runtime edge.

PULSE_JAVASCRIPT_GRAPH_MODULE_MISSING — Javascript Graph Module Missing#

A JavaScript graph edge or entry references a missing graph module.

• Category: internal
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Rebuild the JavaScript plan from the exact source tree and retain the graph manifest.

PULSE_JAVASCRIPT_MODULE_KIND_UNSUPPORTED — Javascript Module Kind Unsupported#

The JavaScript loader encountered a module kind outside its sealed contract.

• Category: internal
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Retain the application plan and report the unsupported module kind.

Safety diagnostics#

PULSE_JAVASCRIPT_MODULE_OUTSIDE_WORKSPACE — Javascript Module Outside Workspace#

A graph-owned project module escapes the authoritative workspace.

• Category: safety
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI build behavior

Remediation

1. Keep every graph-owned project module inside the authoritative Pulse workspace.

PULSE_JAVASCRIPT_MODULE_SOURCE_CHANGED — Javascript Module Source Changed#

A graph-owned project module changed after the JavaScript plan was created.

• Category: safety
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI build behavior

Remediation

1. Rebuild the JavaScript application plan after changing a project module.

PULSE_BUILD_OUT_UNSAFE — Build Out Unsafe#

The resolved build output can escape or alias outside the project root.

• Category: safety
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI build behavior

Remediation

1. Choose an output directory that is a real child of the project root.
2. Do not use .., external absolute paths, or symbolic-link traversal.

Provider diagnostics#

PULSE_PROVIDER_UNSUPPORTED — Provider Unsupported#

The selected provider value is not a supported shorthand or package selection.

• Category: provider
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Select a bare provider id or an exact installed scoped provider package name.

PULSE_PROVIDER_PACKAGE_NOT_FOUND — Provider Package Not Found#

The exact configured provider package does not expose a resolvable toolchain entry.

• Category: provider
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Install the exact configured provider package in the project.
2. Confirm that its package manifest exports ./toolchain.

PULSE_PROVIDER_TOOLCHAIN_LOAD_FAILED — Provider Toolchain Load Failed#

The selected provider package toolchain failed while loading.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Inspect the selected provider package and its dependency installation.
2. Treat provider toolchains as trusted project build code.

PULSE_PROVIDER_TOOLCHAIN_INVALID — Provider Toolchain Invalid#

The selected provider package does not satisfy the versioned toolchain contract.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Use a provider package implementing pulse.provider-toolchain.v1 at ./toolchain.
2. Confirm the declared package name, provider id, and driver shape.

PULSE_BUILD_PROVIDER_REQUIRED — Build Provider Required#

pulse build requires a configured deployment provider; provider-neutral output belongs to pulse compile.

• Category: provider
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Select an executable host in the active .pulse/config.ts profile.
2. Use pulse compile when only provider-neutral Wasm is required.

PULSE_FASTLY_EVENT_INGRESS_UNSUPPORTED — Fastly Event Ingress Unsupported#

Fastly does not expose the host-neutral event ingress required by the application.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 501
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Select Node JavaScript or Node Native for event execution, or use none for compile-only inspection.
2. Do not map event ingress through HTTP or GRIP.

PULSE_FASTLY_EVENT_EMIT_UNSUPPORTED — Fastly Event Emit Unsupported#

Fastly does not expose the host-neutral event acceptance operation required by the application.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 501
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Remove the reachable event.emit requirement or select Node JavaScript or Node Native.
2. Pulse will not substitute logging, HTTP, GRIP, or another target.

PULSE_FASTLY_BACKEND_REQUIRED — Fastly Backend Required#

A static Fastly outbound origin has no configured backend and dynamic backends are disabled.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Declare a static Fastly backend binding for the requested origin, or explicitly enable dynamic backends.

PULSE_FASTLY_BACKEND_BINDINGS_INVALID — Fastly Backend Bindings Invalid#

The Fastly backend binding map is not a valid string-to-string mapping.

• Category: provider
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Correct the Fastly backends map in the active .pulse/config.ts profile.

PULSE_FASTLY_KV_BINDINGS_INVALID — Fastly KV Bindings Invalid#

The Fastly KV binding map is not a valid string-to-string mapping.

• Category: provider
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Correct the Fastly kv binding map in the active .pulse/config.ts profile.

PULSE_FASTLY_GRIP_FANOUT_BACKEND_REQUIRED — Fastly GRIP Fanout Backend Required#

A GRIP hold operation requires a configured Fastly Fanout backend.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Configure the Fastly Fanout backend required by grip.hold.

PULSE_FASTLY_GRIP_PUBLISH_BINDING_REQUIRED — Fastly GRIP Publish Binding Required#

A GRIP publish operation requires configured Fastly publish URL and backend bindings.

• Category: provider
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Fastly provider configuration

Remediation

1. Configure the Fastly GRIP publish backend and URL binding.

Toolchain diagnostics#

PULSE_NODE_VERSION_UNSUPPORTED — Node Version Unsupported#

The active Node.js version is outside the supported release range.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Use a Node.js version matching ^22.14.0 || ^24.0.0 and rerun pulse doctor.

PULSE_FETCH_IMPLEMENTATION_UNAVAILABLE — Fetch Implementation Unavailable#

No supported local fetch implementation is available for the requested operation.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Use a Node.js version matching ^22.14.0 || ^24.0.0, or disable live network fetch and configure deterministic fetch fixtures.

PULSE_CANONICAL_NATIVE_COMPILE_FAILED — Canonical Native Compile Failed#

The provider-neutral native plan could not be compiled into Pulse-owned WebAssembly.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Restore the lockfile-pinned AssemblyScript dependency and rerun pulse doctor.
2. Retain the generated diagnostic detail if AssemblyScript rejects valid Pulse output.

PULSE_FASTLY_CLI_UNAVAILABLE — Fastly CLI Unavailable#

The Fastly executable required for local target execution is unavailable.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Install the Fastly CLI with Homebrew, a supported package manager, or an official release.
2. Ensure fastly is on PATH, or set PULSE_FASTLY_BIN in CI.

PULSE_FASTLY_CLI_INSPECTION_FAILED — Fastly CLI Inspection Failed#

Pulse could not inspect the installed Fastly CLI version.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Run fastly version directly and fix the Fastly CLI installation.

PULSE_VICEROY_UNAVAILABLE — Viceroy Unavailable#

The explicitly selected Viceroy override is unavailable.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Unset PULSE_VICEROY_BIN to let the Fastly CLI manage its local Compute engine.
2. If an override is required, point PULSE_VICEROY_BIN at an executable Viceroy binary.

PULSE_VICEROY_INSPECTION_FAILED — Viceroy Inspection Failed#

Pulse could not inspect the explicitly selected Viceroy override.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Inspect or replace the explicitly selected Viceroy override, or unset it to restore Fastly CLI ownership.

PULSE_FASTLY_SERVE_START_FAILED — Fastly Serve Start Failed#

The Fastly local Compute service failed before becoming ready.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Run fastly compute serve directly in the generated package and inspect its output.

PULSE_FASTLY_SERVE_START_TIMEOUT — Fastly Serve Start Timeout#

The Fastly local Compute service did not become ready before its startup timeout.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Inspect Fastly CLI output and local port availability, then retry.

PULSE_FASTLY_REQUEST_TIMEOUT — Fastly Request Timeout#

A request to the local Fastly Compute service exceeded its timeout.

• Category: toolchain
• CLI exit class: 5
• Development HTTP status: 504
• Stability/scope: preview-stable / public
• Related reference: CLI doctor behavior

Remediation

1. Inspect the local Fastly Compute service and backend fixture before retrying.

Schema diagnostics#

PULSE_SCHEMA_COMPILE_FAILED — Schema Compile Failed#

An explicitly declared JSON schema could not be compiled.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Fix the declared schema source, exported type, or supported field shape.
2. Run pulse doctor --json to inspect schema diagnostics.

PULSE_CANONICAL_SCHEMA_MISSING — Canonical Schema Missing#

The handler references a schema ID that is absent from project configuration.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Declare the referenced schema ID in the default-exported registry selected by pulse.schema.

PULSE_SCHEMA_JSON_DECLARATIONS_RETIRED — Schema JSON Declarations Retired#

Legacy jsonSchemas declarations are no longer accepted as schema authority.

• Category: schema
• CLI exit class: 2
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Move schema declarations into a default-exported defineSchemaRegistry(...) module.
2. Point pulse.schema at that workspace-relative module.

PULSE_SCHEMA_CODEC_REALIZATION_PENDING — Schema Codec Realization Pending#

The selected schema shape cannot be realized by every configured execution target.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Rebuild from the authoritative pulse.schema registry with a compiler that realizes the declared shape on both targets.
2. Pulse will not fall back to generic JSON automatically.

PULSE_CANONICAL_SCHEMA_ID_LITERAL_REQUIRED — Canonical Schema Id Literal Required#

A schema operation uses a value that is not a static string literal ID.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Use a static string literal for the schema ID.

PULSE_SCHEMA_ID_INVALID — Schema Id Invalid#

A schema-bound operation received an invalid schema ID.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Use a non-empty schema ID declared by the authoritative pulse.schema registry.

PULSE_SCHEMA_REQUIRED — Schema Required#

Strict JSON operation omitted its required registered schema ID.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Supply a statically declared schema ID at every strict JSON boundary.

PULSE_SCHEMA_REFERENCE — Schema Reference#

A JSON operation references a schema absent from the compiled codec table.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Reference an ID declared by the authoritative pulse.schema registry.

PULSE_SCHEMA_CODECS_UNAVAILABLE — Schema Codecs Unavailable#

A schema-bound JSON operation has no compiled codec table.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Rebuild or redeploy the application with its generated schema codec table.

PULSE_RESPONSE_CASE_MISSING — Response Case Missing#

The handler references a response case absent from pulse.schema.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Declare the referenced response case in pulse.schema.

PULSE_RESPONSE_CASE_REFERENCE — Response Case Reference#

A runtime JSON response references an unknown compiled response case.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Use a response-case ID declared by pulse.schema.

PULSE_RESPONSE_DESCRIPTOR_INVALID — Response Descriptor Invalid#

A runtime JSON response received an invalid descriptor.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Pass an object descriptor or a registered response-case string to ctx.json.

PULSE_RESPONSE_DESCRIPTOR_LITERAL_REQUIRED — Response Descriptor Literal Required#

A JSON response descriptor cannot be resolved statically.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Use an object literal or a registered response-case string literal as the ctx.json response descriptor.

PULSE_SCHEMA_ID_DUPLICATE — Schema Id Duplicate#

Two or more configured schema declarations use the same stable ID.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Give every declared schema a unique stable ID.

PULSE_SCHEMA_SOURCE_REQUIRED — Schema Source Required#

A schema declaration is missing its project-relative TypeScript source file.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Set the schema declaration source to a project-relative TypeScript file.

PULSE_SCHEMA_TYPE_REQUIRED — Schema Type Required#

A schema declaration is missing its exported TypeScript type name.

• Category: schema
• CLI exit class: 3
• Development HTTP status: 500 fallback when surfaced by the development server
• Stability/scope: preview-stable / public
• Related reference: Project schema configuration

Remediation

1. Set the schema declaration type to an exported TypeScript type name.

Request diagnostics#

PULSE_SCHEMA_CONTENT_TYPE — Schema Content Type#

A schema-bound JSON input uses a content type rejected by policy.

• Category: request
• CLI exit class: 4
• Development HTTP status: 415
• Stability/scope: preview-stable / public
• Related reference: Body and schema troubleshooting

Remediation

1. Send a JSON content type accepted by the configured schema policy.

PULSE_SCHEMA_JSON_MALFORMED — Schema JSON Malformed#

A schema-bound JSON input is not syntactically valid JSON.

• Category: request
• CLI exit class: 4
• Development HTTP status: 400
• Stability/scope: preview-stable / public
• Related reference: Body and schema troubleshooting

Remediation

1. Send syntactically valid JSON before schema validation.

PULSE_BODY_DECODE — Body Decode#

A structured request body could not be decoded in the requested representation.

• Category: request
• CLI exit class: 4
• Development HTTP status: 400
• Stability/scope: preview-stable / public
• Related reference: Body and schema troubleshooting

Remediation

1. Send valid JSON or text matching the documented request shape.

PULSE_SCHEMA_DECODE — Schema Decode#

JSON input did not satisfy the explicitly declared schema and content-type policy.

• Category: request
• CLI exit class: 4
• Development HTTP status: 400
• Stability/scope: preview-stable / public
• Related reference: Body and schema troubleshooting

Remediation

1. Send JSON with the required content type and schema fields.
2. Use pulse test with a failing case to reproduce the validation error locally.

PULSE_BODY_TOO_LARGE — Body Too Large#

A structured body exceeded the configured bounded-body limit.

• Category: request
• CLI exit class: 4
• Development HTTP status: 413
• Stability/scope: preview-stable / public
• Related reference: Body and schema troubleshooting

Remediation

1. Reduce the request payload or increase the configured structured-body limit deliberately.

PULSE_REQUEST_BODY_TOO_LARGE — Request Body Too Large#

An incoming development request exceeded dev.maxBodyBytes.

• Category: request
• CLI exit class: 4
• Development HTTP status: 413
• Stability/scope: preview-stable / public
• Related reference: Body and schema troubleshooting

Remediation

1. Reduce the request payload or increase dev.maxBodyBytes deliberately.

Runtime diagnostics#

PULSE_FETCH_SCHEMA_WITHOUT_JSON — Fetch Schema Without JSON#

An outbound fetch schema was supplied without a semantic JSON payload.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Use schema only together with the outbound fetch json field.

PULSE_BODY_UNAVAILABLE — Body Unavailable#

A structured body was requested when the provider had not supplied one.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Ensure the provider supplied a structured body snapshot before decoding it.

PULSE_OPAQUE_BODY_INSPECTION — Opaque Body Inspection#

Application code attempted to inspect or transform an opaque host-owned body.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 400
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Return or proxy the opaque response directly; do not call JSON, text, bytes, or transform helpers.

PULSE_RESPONSE_ENCODE — Response Encode#

The selected response encoder cannot represent the returned value.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Return a value supported by the selected response or schema encoder.

PULSE_SCHEMA_ENCODE — Schema Encode#

The returned value does not satisfy its declared response schema.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Return a value that satisfies the declared response schema.

PULSE_FETCH_TIMEOUT — Fetch Timeout#

An outbound fetch did not complete before its timeout.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 504
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Check the origin and timeout policy, then retry.
2. Use a configured fetch fixture in tests for deterministic reproduction.

PULSE_FETCH_NETWORK — Fetch Network#

An outbound fetch failed because the origin or network was unavailable.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 502
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Check the origin URL, backend binding, and local network access.

PULSE_FETCH_URL_INVALID — Fetch URL Invalid#

An outbound fetch uses an invalid or unsupported URL.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 400
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Use an absolute supported URL or a correctly configured provider backend.

PULSE_CONTINUATION_EXPIRED — Continuation Expired#

A pending continuation exceeded its configured lifetime before resumption.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 504
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Increase the continuation TTL only if the provider operation is expected to take longer.

PULSE_CONTINUATION_DOUBLE_RESUME — Continuation Double Resume#

A provider attempted to resume the same continuation more than once.

• Category: runtime
• CLI exit class: 4
• Development HTTP status: 500
• Stability/scope: preview-stable / public
• Related reference: Troubleshooting

Remediation

1. Report this as a Pulse runtime/provider bug with the continuation trace.