Timing control
Wait before continuing to the next action.
Delay component
Use Delay when the next action should wait for time, an external system, or a controlled retry window.
Pause workflow execution for a configured amount of time before continuing.
What this component unlocks
The docs describe Delay as a component for introducing pauses in a workflow so actions occur at the right time and in the right sequence. Builders configure the delay amount and choose a time unit: milliseconds, seconds, or minutes. The component is useful when a workflow needs to wait for an external service to update before continuing.
Wait before continuing to the next action.
Give external systems time to update before the workflow checks or acts again.
Control the timing of actions so operations happen in the intended order.
Use cases
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
Configuration surface
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Use longer delays intentionally.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Make retry loops visible.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Test the configured delay to confirm the timing matches the workflow requirement.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Start with an event, use Delay, then route the result to CRM, ticketing, or a customer-owned system.
Add validation, human approval, and logging around the component before downstream actions execute.
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.