Pipeline Operation: Manual Step

Pause pipeline execution and request user confirmation or manual approval before continuing to the next step.

The Manual Step operation allows you to insert a controlled pause within a pipeline, requiring human confirmation or input before continuing.It’s used for approvals, validations, or manual checks (for example, “Create User before deployment”) that must be completed before the next automated stage runs.

Manual Steps help teams ensure that sensitive operations are verified or approved before continuing execution.

Creating a Manual Step

1. Go to Pipelines → Create or Edit an existing pipeline.

2. Click the + icon between Start and Stop.

3. In the configuration panel, set:

   • Name: Create User

   • Operation: ManualStep

   • Description: Create User before deployment

   • On pass: Stop

4. Click Add to save the configuration.

Tip: Manual Steps can be positioned anywhere in the pipeline — before or after Webhook, Deploy, or Validate steps.

Running a Pipeline

1. Click Run pipeline from the top-right corner.

2. The pipeline starts execution and pauses when it reaches the Manual Step.

3. A blue banner appears at the top labeled Action Required, indicating that the pipeline is waiting for user input.

4. Perform the requested manual action (e.g., create a user in Salesforce).

5. Click Continue to resume execution.

Action Required State

When the pipeline reaches a Manual Step:

• Execution halts and displays Action Required.

• The step remains paused until a user clicks Continue.

• Any authorized team member can view and continue the step.

• Once resumed, the pipeline continues or stops as configured.

This ensures that validation or approval tasks are completed before automated jobs proceed.

Example Execution

Scenario: A pipeline named Validate Pipeline includes a Manual Step titled Create User.

Process Flow:

1. Pipeline starts from the Start node.

2. Execution pauses at Create User → status changes to Action Required.

3. The user performs the described task (e.g., creates the user in Salesforce).

4. Click Continue to proceed.

5. Pipeline completes successfully — status changes to Completed, and a green banner appears: Pipeline ran successfully.

Viewing Results

After running the pipeline:

1. Navigate to Code → Branch → Activities → Pipelines.

2. Each job displays key details:

   • Type: ManualStep

   • Status: Completed / Action Required

   • Duration: Total runtime (including pause time)

   • Created by: User who continued the step

3. Click the pipeline name (e.g., QA Team Pipeline) to view detailed logs.

Sample Logs:

[Info] Job started  
[Info] Manual step paused – awaiting action  
[Info] Manual step continued by user  
[Info] Job completed successfully  

Best Practices

• Use Manual Steps for approvals, validations, or manual checkpoints.

• Always include a clear description so team members know what to do.

• Place Manual Steps before critical operations like Deploy or Rollback.

• Regularly review Activities → Pipelines to verify who approved each step.

• Avoid leaving steps idle — pipelines remain paused until resumed.