/**
 * Runs the job under a deadline that CANCELS it rather than merely giving up on
 * it: the signal reaches `executeJob`, which cancels the in-flight query and
 * rolls back, so a timed-out job stops holding its transaction and its backend.
 * The abort reason is the timeout error, so that is what the job fails with.
 *
 * The deadline still holds for a handler that ignores its signal: the wait ends
 * on abort either way, so the worker slot is freed on time and the job is
 * recorded as failed — the signal is what additionally frees the backend.
 */
export declare function executeWithTimeout<T>(fn: (signal?: AbortSignal) => Promise<T>, timeoutMs: number | undefined, jobType: string, jobId: string): Promise<T>;
//# sourceMappingURL=job-timeout.d.ts.map