Skip to main content

Namespace: activity

This package's main export is Context. Get the current Activity's context with Context.current():

import { Context } from '@temporalio/activity';

export async function myActivity() {
const context = Context.current();
}

Any function can be used as an Activity as long as its parameters and return value are serializable using a DataConverter.

Cancellation

Activity Cancellation:

  • lets the Activity know it doesn't need to keep doing work, and
  • gives the Activity time to clean up any resources it has created.

Activities can only receive Cancellation if they emit heartbeats or are Local Activities (which can't heartbeat but receive Cancellation anyway).

An Activity may receive Cancellation if:

  • The Workflow scope containing the Activity call was requested to be Cancelled and ActivityOptions.cancellationType was not set to ActivityCancellationType.ABANDON. The scope can be cancelled in either of the following ways:
    • The entire Workflow was Cancelled (via WorkflowHandle.cancel).
    • Calling CancellationScope.cancel) from inside a Workflow.
  • The Worker has started to shut down. Shutdown is initiated by either:
    • One of the RuntimeOptions.shutdownSignals was sent to the process.
    • Worker.shutdown | Worker.shutdown() was called.
  • The Activity was considered failed by the Server because any of the Activity timeouts have triggered (for example, the Server didn't receive a heartbeat within the ActivityOptions.heartbeatTimeout). The CancelledFailure will have message: 'TIMED_OUT'.
  • An Activity sends a heartbeat with Context.current().heartbeat() and the heartbeat details can't be converted by the Worker's configured DataConverter.
  • The Workflow Run reached a Closed state, in which case the CancelledFailure will have message: 'NOT_FOUND'.

The reason for the Cancellation is available at CancelledFailure.message or Context.cancellationSignal.reason.

Activity implementations should opt-in and subscribe to cancellation using one of the following methods:

  1. await on Context.current().cancelled or Context.current().sleep(), which each throw a CancelledFailure.
  2. Pass the context's AbortSignal at Context.current().cancellationSignal to a library that supports it.

Examples

An Activity that sends progress heartbeats and can be Cancelled

import { activityInfo, log, sleep, CancelledFailure, heartbeat } from '@temporalio/activity';

export async function fakeProgress(sleepIntervalMs = 1000): Promise<void> {
try {
// allow for resuming from heartbeat
const startingPoint = activityInfo().heartbeatDetails || 1;
log.info('Starting activity at progress', { startingPoint });
for (let progress = startingPoint; progress <= 100; ++progress) {
// simple utility to sleep in activity for given interval or throw if Activity is cancelled
// don't confuse with Workflow.sleep which is only used in Workflow functions!
log.info('Progress', { progress });
await sleep(sleepIntervalMs);
heartbeat(progress);
}
} catch (err) {
if (err instanceof CancelledFailure) {
log.warn('Fake progress activity cancelled', { message: err.message });
// Cleanup
}
throw err;
}
}

An Activity that makes a cancellable HTTP request

It passes the AbortSignal to fetch: fetch(url, { signal: Context.current().cancellationSignal }).

import fetch from 'node-fetch';
import { cancellationSignal, heartbeat } from '@temporalio/activity';
import type { AbortSignal as FetchAbortSignal } from 'node-fetch/externals';

export async function cancellableFetch(url: string): Promise<Uint8Array> {
const response = await fetch(url, { signal: cancellationSignal() as FetchAbortSignal });
const contentLengthHeader = response.headers.get('Content-Length');
if (contentLengthHeader === null) {
throw new Error('expected Content-Length header to be set');
}
const contentLength = parseInt(contentLengthHeader);
let bytesRead = 0;
const chunks: Buffer[] = [];

for await (const chunk of response.body) {
if (!(chunk instanceof Buffer)) {
throw new TypeError('Expected Buffer');
}
bytesRead += chunk.length;
chunks.push(chunk);
heartbeat(bytesRead / contentLength);
}
return Buffer.concat(chunks);
}

Classes

Interfaces

References

ActivityFunction

Re-exports ActivityFunction


ActivityInterface

Re-exports ActivityInterface


ApplicationFailure

Re-exports ApplicationFailure


CancelledFailure

Re-exports CancelledFailure


UntypedActivities

Re-exports UntypedActivities

Variables

asyncLocalStorage

Const asyncLocalStorage: AsyncLocalStorage<Context>


log

Const log: Logger

The logger for this Activity.

This is a shortcut for Context.current().log (see Context.log).

Functions

activityInfo

activityInfo(): Info

The current Activity's context.

Returns

Info


cancellationSignal

cancellationSignal(): AbortSignal

Return an AbortSignal that can be used to react to Activity cancellation.

This can be passed in to libraries such as fetch to abort an in-progress request and child_process to abort a child process, as well as other built-in node modules and modules found on npm.

Note that to get notified of cancellation, an activity must also do Context.heartbeat.

This is a shortcut for Context.current().cancellationSignal (see Context.cancellationSignal).

Returns

AbortSignal


cancelled

cancelled(): Promise<never>

Return a Promise that fails with a CancelledFailure when cancellation of this activity is requested. The promise is guaranteed to never successfully resolve. Await this promise in an Activity to get notified of cancellation.

Note that to get notified of cancellation, an activity must also do Context.heartbeat.

This is a shortcut for Context.current().cancelled (see Context.cancelled).

Returns

Promise<never>


heartbeat

heartbeat(details?): void

Send a heartbeat from an Activity.

If an Activity times out, then during the next retry, the last value of details is available at Info.heartbeatDetails. This acts as a periodic checkpoint mechanism for the progress of an Activity.

If an Activity times out on the final retry (relevant in cases in which RetryPolicy.maximumAttempts is set), the Activity function call in the Workflow code will throw an ActivityFailure with the cause attribute set to a TimeoutFailure, which has the last value of details available at TimeoutFailure.lastHeartbeatDetails.

This is a shortcut for Context.current().heatbeat(ms) (see Context.heartbeat).

Parameters

NameType
details?unknown

Returns

void


sleep

sleep(ms): Promise<void>

Helper function for sleeping in an Activity.

This is a shortcut for Context.current().sleep(ms) (see Context.sleep).

Parameters

NameTypeDescription
msDurationSleep duration: number of milliseconds or ms-formatted string

Returns

Promise<void>

A Promise that either resolves when ms is reached or rejects when the Activity is cancelled