Delay component

Component Logic & Flow Governed workflow step Customer-owned runtime

Delay for customer-owned automation.

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.

Delay Component
DelayPause execution for a configured amount of milliseconds, seconds, or minutes.
CX CXFabric Flow Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval

What this component unlocks

Use Delay as a visible flow step.

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.

Timing control

Wait before continuing to the next action.

External service wait

Give external systems time to update before the workflow checks or acts again.

Sequence management

Control the timing of actions so operations happen in the intended order.

Use cases

Where Delay fits in automation.

These examples show how this component can become part of production workflows across customer-owned systems and environments.

Component

Retry window

Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.

  • Collect the approved input
  • Apply customer-specific rules
  • Pass a clear result to the next step
Component

Deferred notification

Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.

  • Collect the approved input
  • Apply customer-specific rules
  • Pass a clear result to the next step
Component

External system wait

Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.

  • Collect the approved input
  • Apply customer-specific rules
  • Pass a clear result to the next step
Component

Backoff flow

Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.

  • Collect the approved input
  • Apply customer-specific rules
  • Pass a clear result to the next step
Component

Timed handoff

Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.

  • Collect the approved input
  • Apply customer-specific rules
  • Pass a clear result to the next step
Component

Rate-limit spacing

Use Delay as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.

  • Collect the approved input
  • Apply customer-specific rules
  • Pass a clear result to the next step

Configuration surface

Practical options builders expect to use.

The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.

Component

Add Delay to canvas

Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.

Component

Open component settings

Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.

Component

Enter delay amount

Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.

Component

Choose milliseconds, seconds, or minutes

Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.

Component

Submit configuration

Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.

Component

Execute and review logs

Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.

Implementation notes

Design the step with operations in mind.

Components should be easy for builders to configure and easy for operators to understand after the workflow is live.

Planning note

Use longer delays intentionally

Use longer delays intentionally.

CXFabric approach

Make the behavior explicit in the workflow so operators can see what happens before and after this component runs.

Planning note

Make retry loops visible

Make retry loops visible.

CXFabric approach

Make the behavior explicit in the workflow so operators can see what happens before and after this component runs.

Planning note

Test the configured delay to confirm the timing matches the workflow requirement

Test the configured delay to confirm the timing matches the workflow requirement.

CXFabric approach

Make the behavior explicit in the workflow so operators can see what happens before and after this component runs.

Workflow patterns

Reusable patterns for Delay.

These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.

Delay in a customer intake flow

Start with an event, use Delay, then route the result to CRM, ticketing, or a customer-owned system.

Delay with approval and audit

Add validation, human approval, and logging around the component before downstream actions execute.

Delay in a private runtime

Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.

Delay plus custom connector

Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.

Component planning

Need Delay inside a customer workflow?

We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.

We will use this to follow up about your CXFabric workflow.