(entry: QueueEntry<T>): Effect.Effect<void, never, R>
(entries: ReadonlyArray<QueueEntry<T>>): Effect.Effect<void, never, R>Re-inject existing QueueEntrys (single or array) — the inverse of release, and the
input you get straight off the QueueHandleApi.events stream. Unlike QueueEnqueue
(raw items T, you pick the priority), each entry re-enters at its own priority with its
attempts count preserved (so a job mid-retry keeps its budget). For handoff / event
round-trips: yield* queue.enqueue(event.entries).
export interface interface QueueEnqueueEntries<T, R = never>Re-inject existing
QueueEntry
s (single or array) — the inverse of release, and the
input you get straight off the
QueueHandleApi.events
stream. Unlike
QueueEnqueue
(raw items T, you pick the priority), each entry re-enters at its own priority with its
attempts count preserved (so a job mid-retry keeps its budget). For handoff / event
round-trips: yield* queue.enqueue(event.entries).
QueueEnqueueEntries<function (type parameter) T in QueueEnqueueEntries<T, R = never>T, function (type parameter) R in QueueEnqueueEntries<T, R = never>R = never> {
(entry: QueueEntry<T>(parameter) entry: {
item: T;
entryId: string;
key: string;
priority: Priority;
lane: number;
attempts: number;
timestamps: QueueEntryTimestamps;
batchId: string;
releaseId: string;
sourceHyperlinkId: string;
attributes: { readonly [key: string]: unknown };
}
interface QueueEntry<T>QueueEntry<function (type parameter) T in QueueEnqueueEntries<T, R = never>T>): import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<void, never, function (type parameter) R in QueueEnqueueEntries<T, R = never>R>;
(entries: ReadonlyArray<QueueEntry<T>>entries: interface ReadonlyArray<T>ReadonlyArray<interface QueueEntry<T>QueueEntry<function (type parameter) T in QueueEnqueueEntries<T, R = never>T>>): import EffectEffect.interface Effect<out A, out E = never, out R = never>The Effect interface defines a value that lazily describes a workflow or
job. The workflow requires some context R, and may fail with an error of
type E, or succeed with a value of type A.
When to use
Use when you need to represent a lazy, composable workflow that can require
services, fail with a typed error, or succeed with a typed value.
Details
Effect values model resourceful interaction with the outside world,
including synchronous, asynchronous, concurrent, and parallel interaction.
They use a fiber-based concurrency model, with built-in support for
scheduling, fine-grained interruption, structured concurrency, and high
scalability.
To run an Effect value, you need a Runtime, which is a type that is
capable of executing Effect values.
Effect<void, never, function (type parameter) R in QueueEnqueueEntries<T, R = never>R>;
}