Follow one execution
Deliver one typed failure Cause with no successful value.
failTick 0. Subscription: start.
Read this diagram
Follow each lane from left to right. Events stacked vertically share a tick; the green cursor marks the current time across every lane.
- A value
The text inside the pill is the emitted value. - Work starts
The raised chevron starts an inner run (^in the source). - The run returns
The vertical bar ends this lane’s run. - A cause is delivered
The exclamation mark belongs to this lane. - Work is interrupted
The cross marks cancellation of this run. - Current time
The line and diamond move together across all lanes. - Happening now
A highlighted event is at the current tick. - Still ahead
Muted, dashed values have not happened yet. - Time continues
The lane’s arrow is not a return marker. An empty stretch can be quiet work that is still running.
Illustrated ticks start at 0. At 1×, one illustrated tick takes one second; captions specify real durations when timing matters. A cause or interruption belongs to its lane, and other work may continue. Scroll horizontally to inspect the rest of a long timeline.
Construction is inert. Each run delivers one typed failure cause to the sink and acquires no resources.
Import
import { fail } from "@typed/fx/Fx";Signatures
export declare const fail: <E>(error: E) => Fx<never, E, never>;Why
fail introduces an expected domain error into the typed E channel without
emitting a value.
Ownership and lifetime
Construction is inert. Each run delivers one typed failure cause to the sink and acquires no resources.
Examples
import { Effect } from "effect"
import { fail, first } from "@typed/fx/Fx"
const program = first(fail("offline")).pipe(
Effect.catch((error) => Effect.succeed(`failed: ${error}`))
)Other public imports
These import paths expose the same declaration. Each page retains its own public name and signature.