Task operations allow your connector to schedule recurring background work, fan out into smaller units of work, and report execution status back to the platform. They are how a connector keeps data in Teamwork Graph fresh without needing an external scheduler.

A connector that uses task operations declares a taskRunner function in its manifest, schedules a recurring root task per connection, and (optionally) schedules child tasks during each root invocation to fan out the work.

Before using these methods, read Orchestration concepts for the IDs, idempotency rules, and lifecycle you need to design around.

Available methods

Method	Description
`scheduleOrUpdateTask`	Schedule a recurring root task that the platform invokes on a fixed cadence, or update an existing schedule in place. See scheduleOrUpdateTask.
`scheduleChildTask`	Schedule a one-off child task from inside a running task invocation. Used to fan out work into smaller units. See scheduleChildTask.
`updateTaskStatus`	Report the success or failure of one task invocation back to the platform. See updateTaskStatus.
`taskRunner`	The function module the platform invokes for every scheduled task. Defines the payload shape and execution contract. See taskRunner.