Service Nodes
A service node represents a service that is connected to Requence. When execution reaches this node, it dispatches a message to the service and waits for a response.
When a service defines a configuration schema, the configuration values must be provided in the visual editor.
Settings
Section titled “Settings”Each service node has three configurable settings, accessible via the settings button (gear icon) on the node:
- Time to respond — maximum time in milliseconds the node will wait for a response before failing. Defaults to infinite.
- Retry — number of times the node will automatically retry after a failure. Defaults to none.
- Retry delay — delay in milliseconds between retry attempts. Defaults to none.
How Defaults Work
Section titled “How Defaults Work”Settings are resolved using a three-tier system. Each property is resolved independently:
- Manual value — if you explicitly set a value on the node, it takes highest priority
- Version default — if the service version defines a default for this property, it is used
- Global default — no retry, infinite time to respond
The settings button on the node highlights when you have made manual overrides. When a node uses version or global defaults, the button stays unhighlighted and the default values appear as placeholders in the settings popover.
Interaction with Version Changes
Section titled “Interaction with Version Changes”When you switch a service node to a different version:
- Manual overrides are preserved — your explicit values are never overwritten
- Non-manual properties pick up the new version’s defaults automatically