Task Templates

A task template is the blueprint for a task. It defines the services involved, how data flows between them, and the rules for execution.

Every task template starts with an entry node and usually ends with one or more exit nodes. The entry node receives the input payload when a task is started, and exit nodes mark the end of the task, capturing the final output. Continuous task templates are an exception — they may not have exit nodes.

Creating a Task Template

1. Open the Requence dashboard
2. Navigate to Task Templates
3. Click New Task Template and give it a name

The visual editor opens with the simplest template: an entry node with no input schema directly connected to an exit node with no output schema. From here you can add service nodes, connect them, and configure the flow.

Error Handling

Service, logic, and sub task nodes always have an additional on fail output. You can connect this output to other nodes to handle errors gracefully. If the on fail output is not connected and an error occurs, the task terminates immediately.

Connecting Nodes

Drag edges between nodes to define execution order. When a node has multiple incoming edges, all upstream dependencies must complete successfully before it executes — multiple inputs are treated as AND by design. The only exception is the Or node, which fires as soon as a single input arrives.

Tip

You can optionally assign an alias to service, logic, exit, and sub task nodes. Aliases give nodes a human-readable name, making it easier to identify them and reference their output from other nodes.