Environment

Tasks
Runs
Batches
Schedules
Queues
Waitpoint tokens
Deployments
Test

Manage

Bulk actions
API keys
Environment variables
Alerts
Preview branches
Regions
Limits

Project settings

General
Integrations

Test

Test docs

merry.w3.verify-demand-timing

2026
06
12
11
39
10
AM

This is the timestamp of the CRON, it will come through to your run in the payload.

This is the timestamp of the previous run. You can use this in your code to find new data since the previous run.

The Timestamp and Last timestamp are in UTC so this just changes the timezone string that comes through in the payload.

Optionally, you can specify your own IDs (like a user ID) and then use it inside the run function of your task. Read the docs.

Options enable you to control the execution behavior of your task. Read the docs.

Overrides the machine preset.

Only the latest version is available in the development environment.

Assign run to a specific queue.

Add tags to easily filter runs.

Retries failed runs up to the specified number of attempts.

h
m
s

Overrides the maximum compute time limit for the run.

Specify an idempotency key to ensure that a task is only triggered once with the same key.

h
m
s

Keys expire after 30 days by default.

Limits concurrency by creating a separate queue for each value of the key.

h
m
s

Sets the priority of the run. Higher values mean higher priority.

h
m
s

Expires the run if it hasn't started within the TTL.

This test will run in

Development
,