---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Change acceleration for manual jobs

# Change acceleration for manual jobs {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Enable change tracking for the pipeline in the tool record page in DevOps Change Velocity.
The GitLab job under change control must have these instructions for the pipeline execution to be resumed or canceled via the change request:

* when: <kbd class="ph userinput">manual</kbd>
* allow_failure: <kbd class="ph userinput">false</kbd>
{#gitlab-change-manual__ul_onz_xnj_gmb}  
For example:


    deploy:
      stage: deploy
      tags:
        - local-runner1
      when: manual
      allow_failure: false
      script:
        - echo 'Deploy'

Note:  
For when:manual based changes, for a change request to get created at a certain stage, all the previous stages must complete successfully. If any of the previous stages is not invoked or not successful, even though there is no dependency of the current stage on its immediate previous stage, a change request will not get created in ServiceNow.

GitLab pipeline parallel stages is supported with GitLab Docker Image. For more details, see [GitLab pipelines with parallel jobs](https://servicenow-prod.fluidtopics.net/XxDNpa1Slwg0~F8ONe0cmw "GitLab Docker Image supports change creation in GitLab pipelines containing parallel jobs.") and [Implement custom actions for pipelines using a generic Docker container image](https://servicenow-prod.fluidtopics.net/lyDd5Y1L9yyAuDzJFwe0tg "Use the ServiceNow custom actions to collect data related to change request creation, Sonar scan, artifact registration, and package registration in your pipeline with the help of the generic Docker Container Image.").

Refer to the [CI/CD pipeline configuration reference](https://docs.gitlab.com/) for more information on how to configure a GitLab job.  
Additional considerations:

* If allow_failure is set to <kbd class="ph userinput">true</kbd>, the pipeline continues even when the change is rejected.
* A user with the appropriate role access in GitLab can unblock and continue a pipeline regardless of the change request state.
{#gitlab-change-manual__ul_xry_lxn_mmb}  
{#gitlab-change-manual__table_exk_tmb_gmb__entry__4}

| Manual execution | Change acceleration in step | Change request approved | Result |
|-|-|-|-|
| Yes | Yes | N/A | If the manual job is under change control, the change is automatically created. |
| Yes | Yes | Yes | The manual job is automatically executed. |
| Yes | Yes | No | The manual job is automatically rejected/failed. |
| Yes | No | N/A | The manual job waits for manual intervention from the pipeline owner via the GitLab UI (default behavior). |
| No | Yes | N/A | The change request is not created. |
[Table 1. GitLab change acceleration behavior]

{#gitlab-change-manual__table_exk_tmb_gmb}  
Note:  
Parallel jobs are displayed sequentially, based on the order in which the jobs are queued for execution.