Services

A service is an external process that connects to Requence. You create services in the UI and provide the implementation yourself.

On the planning side, each service is registered in the UI with one or more versions. A service version declares:

• An input schema — the data it expects to receive
• A configuration schema — static settings passed at design time
• One or more outputs — each with its own schema
• Optional default node settings — default retry, retry delay, and time-to-respond values

When you drag a service node onto the canvas in the task template editor, you pick which service version to bind it to. Requence uses the version’s schemas to validate configuration at design time and input/output at execution time.

Default Node Settings

A service version can optionally define default values for:

• Retry — number of automatic retries after failure (1–10)
• Retry delay — delay between retry attempts in milliseconds (100–10,000ms)
• Time to respond — maximum time to wait for a response in milliseconds (min 100ms)

These defaults are applied to every service node that uses this version, unless the node has its own manual override. This is useful when a service should always be retried — you configure it once on the version instead of remembering to set it on every node.