Mergent
Home
Search…
Overview
Tasks
Quick Start
Scheduling Tasks
Request Failures & Retries
Viewing Task History
Request Timeouts
Webhooks Security
Localhost Dev & Webhooks
Schedules
Quick Start
Schedule Types
Request Failures & Retries
Client Libraries
JavaScript / TypeScript
Ruby
Example Implementations
API
Authentication
Errors
Rate Limits
API Reference
API Status
Guides
Encrypting Data
Use Cases
Send External Requests
Powered By GitBook
Scheduling Tasks
Mergent supports multiple ways of scheduling Tasks:
  1. 1.
    ​Tasks that run once can be scheduled directly with the Tasks API using scheduled_for or delay
  2. 2.
    ​Tasks that run periodically (e.g., a cron or iCal RRULE) can be scheduled using Mergent Schedules.

Tasks that run once

Tasks that need to be run only once at a specified time can be scheduled via the Tasks API in two ways: scheduled_for and delay.

scheduled_for

To schedule a task to run once at a specific time, specify the scheduled_for when creating a Task using the ISO 8601 timestamp format.
For example, setting scheduled_for to 2024-01-01T00:00:00Z will schedule the task to run at midnight of January 1, 2024.

delay

To schedule a task to run once after a delay, specify the delay when creating a Task using the ISO 8601 duration format.
For example, a delay of PT5M will delay the Task for 5 minutes.

Tasks that run periodically

Tasks that need to be run periodically can be scheduled via Mergent Schedules.
​Click here to go to our Schedules documentation.
Tasks - Previous
Quick Start
Next - Tasks
Request Failures & Retries
Last modified 6mo ago
Copy link
On this page
Tasks that run once
Tasks that run periodically