Why do I see the completed pipeline status as "Paused"?
Asked by Dinara Tablina:

All my completed pipelines in all repositories today got status "Paused" instead of "Completed". What can be the reason of that changes?


Answers:
author: Edmund Munday
body: Hi all - apologies for the confusion around this change. There are several small incremental changes currently underway designed to give users more a more explicit set of statuses for builds - in addition to giving users more tools to better manage those statuses - what you are seeing right now is one step, of several, that are underway to "rationalise" the way statuses are used, and also give you all more flexibility.

***What's changed so far:***

There have been two changes so far, with a few more to come.

* The first change was purely cosmetic, changing the status colour for "Stopped" builds from an amber "warning" style colour, to a grey "Subtle" style colour.
  * This was done as a build that is "Stoped" has been put into that status via an active decision by a user, therefore it does not need immediate attention and should not be showing a "warning" colour.
* The second change was to make the UI representation of "Paused" steps actually match their underlying status in the system (this is the change that's causing the confusion). Note - this is a UI change only, designed to increase the overall consistency and understandability of the UI. ***No behavioural changes have occurred due to this.***
  * Specifically, this affects Pipelines that contain steps with a "manual" trigger, most often used for manually approving deployments, however also sometimes used to control optional steps that people might run at the end of a pipeline.
  * Important to note that these pipelines have ***always*** been considered "Paused" in the system, and that has ***always*** been reflected in the UI when filtering pipelines by status.
    * When filtering by "Paused" status, these Pipelines have always been displayed.
    * When filtering by "Successful" status, these Pipelines have always been hidden
  * However, the actual text + colour shown in the "Status" column for these pipelines previously showed "Successful", even though that was ***not*** the correct status for these pipelines in the system.
    * This made it effectively impossible to differentiate between pipelines that were actually "Successful", vs ones that were simply "Paused" without using the status filter to seperate the two.
    * It was also highly inconsistent as the status filter did not visually match what the user was seeing in the UI under the "status" column.
  * To be clear, we understand this creates an inconvenience in situations where customers have "paused" pipelines that they have no intention of actually completing, such as when they have got "optional" steps at the end of their workflow controlled via the "manual" trigger.

***What's still coming:***

* The third change that we are planning to implement is designed to address this scenario by allowing customer to manually move a "paused" pipeline out of that "paused" state, and into one of several possible final states.
  * This will allow customers to mark a "Paused" pipeline as "Successful" or potentially some other "Cancelled" state, if they do not intend to execute the manually triggered steps, but do not want to leave it in a "Paused" state.
* ***Future:*** We are also considering the option of marking some steps as explicitly "optional", which would allow them to not affect the overall pipeline status at all. This is a larger change that is not happening in the immediate future though.

***Feedback request:***

* It's clear from the feedback here that, while these changes are making things more consistent and explicit on one side, they may be disrupting peoples workflows on another.
  * Specifically - there is a distinction between when a pipeline is "paused" due to some kind of system controlled mechanism (e.g a deployment lock), where that pipeline ***needs*** human interaction, vs a pipeline that was paused due to a decision made by the user via their pipelines .yml file (e.g a manual trigger).
  * While these are both still "Paused", they are a different in terms of their severity. A system enforced "pause" (referred to as a "halted" state internally) is one that requires relatively immediate manual intervention. A workflow enforced "pause" does not.
  * One simple option would be to seperate these two state's into two distinct options - "Paused" for workflow enforced states (e.g manual triggers), and "Halted" for system enforced.
    * In this scenario, "paused" would show as the green "Success" colour, and "halted" as the amber "Warning" colour.

comments: author: Sebastian C
body: The current state of this is inconsistent with bitbucket documentation. There was already alignment on how this state should be represented.

<https://support.atlassian.com/bitbucket-cloud/docs/view-your-pipeline/#2.-Pipeline-status>

Please revert, or give your customers the option to revert/opt-in. Introduce a new state of "Successful, Incomplete" if that seems more appropriate.

![2024-05-29_11-16-32.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/326698i1DC56FD0536E54BD/image-size/large?v=v2&px=999 "2024-05-29_11-16-32.jpeg")


author: Jim Nidositko
body: [@Edmund Munday](/t5/user/viewprofilepage/user-id/4953583) You have stated yourself the exact problem that people are up in arms about:

*
  > To be clear, we understand this creates an inconvenience in situations where customers have "paused" pipelines that they have no intention of actually completing, such as when they have got "optional" steps at the end of their workflow controlled via the "manual" trigger.

This is more than an inconvenience.

This change to improve "consistency" between backend status and displayed status now takes every build that used to look normal (Successful) and mixed it in with what was previously an exceptional status (Paused) that was only ever displayed *when a user took manual action to pause a build*.

We now have no way to differentiate the most common build outcome / use-case from a highly exceptional / unusual use case.

Please revert this change immediately and (if you feel it is truly necessary) add an option to allow customers to opt into this massive UI change.


author: Leon Komarovsky
body: Actually after reading [@Edmund Munday](/t5/user/viewprofilepage/user-id/4953583) response, I understand how it works now and do see value in it. It focuses developers a bit more on "incomplete" pipelines, pushing them to make them green. It will take some time getting used to the new concept.

The release process of this feature was terrible. This change had to be communicated to all customers BEFORE it was made, and probably several times. You should make sure that as much of your customers as possible understand the change. You introduced conceptually different approach without notifying us properly.


author: Sharon Hinde
body: thx Atlassian for breaking my brain today and making me waste time trying to fix an issue that wasn't actually there.

That new orange Paused status on manual steps made me think the pipelines on my new repository were broken!  

Please revert pipelines with manual steps to Successful because this is currently a broken user experience for teams that rely on pipeline statuses at a glance.


author: Ravi Ponnada
body: The previous functionality of hollow green circle with the green check mark was perfect because we knew that all the executed steps were successful and there are additional manual steps.

This change is confusing and I along with all the developers (I am sure) wish you revert this.


author: Marin
body: This is a breaking change in the UI as it shows a warning color and label for the paused status in pipelines with manual steps, please revert or advise on how to handle it to get the old behavior back. Our team of developers is now unsure of pipelines status because of it.


author: Igor Bljahhin
body: This change is very annoying and inconvenient. Before, all our completed builds were GREEN, which was fine because we executed manual steps very rarely. Now, successfully completed builds are suddenly YELLOW, which makes us worry and wonder if the job successfully finished or if somebody/something paused the job.

Please make this option configurable or revert to the old behavior.

comments: author: Igor Bljahhin
body: I would like to mention as well, that we used to get the notifications about finished jobs to Slack. Now notifications are not coming to Slack because the jobs are not finished, but they are paused!

UPD. This issue was not related to the change in pipelines statuses.


author: Igor Bljahhin
body: I see that you changed the color of Paused builds from yellow to grey. I am okay with this fix. The color was only thing which was annoying us.


author: Andrew Mollerson
body: Currently seeing the same issue as well in our environment. Manual build steps are configured.

![2024-05-28 08_29_06-ttec-digital-ip _ oneview Pipelines ? Bitbucket.png](https://community.atlassian.com/t5/image/serverpage/image-id/326367i62AC6C5435690F1E/image-size/large?v=v2&px=999 "2024-05-28 08_29_06-ttec-digital-ip _ oneview Pipelines ? Bitbucket.png")

Commit messages were masked so this isn't an UI issue


author: Dinara Tablina
body: I suppose that with the latest Bitbucket updates, all pipelines that had unfinished steps (jobs) are now marked as Paused, and pipelines that had all steps completed are marked as Completed.

If I'm right, this is an inconvenient update.

comments: author: Pascal De Cort
body: [@Dinara Tablina](/t5/user/viewprofilepage/user-id/5495660) seems to be correct. Pipelines that have *manual steps* and not executed are marked as paused.

part of the pipeline:  
- step:  
name: Deploy pos-service artifacts to S3  
image: atlassian/pipelines-awscli  
trigger: **manual**  
script:  
- aws s3 cp pos-service/build/libs/p....

check differences in 2 screenshots

![Screenshot 2024-05-28 at 14.01.53.png](https://community.atlassian.com/t5/image/serverpage/image-id/326320i2EA0FA0BD04E5CFB/image-dimensions/220x316?v=v2 "Screenshot 2024-05-28 at 14.01.53.png") ___![Screenshot 2024-05-28 at 14.03.12.png](https://community.atlassian.com/t5/image/serverpage/image-id/326321i8B6D770028BF9279/image-dimensions/222x315?v=v2 "Screenshot 2024-05-28 at 14.03.12.png")


author: Dinara Tablina
body: Hello, [@Pascal De Cort](/t5/user/viewprofilepage/user-id/4989809)

Do you know if it is a consequence of latest Bitbucket updates?


author: Edmund Munday
body: Hi all - please see: <https://community.atlassian.com/t5/Bitbucket-questions/Re-Why-do-I-see-the-completed-pipeline-status-as-quot-Paused/qaq-p/2710948/comment-id/104654#M104654>


author: Sebastian C
body: edited: \[i meant to post this as a reply, not an answer\]


author: Leon Komarovsky
body: Hi [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) , we now have the same problem on our repos.

Running a pipeline that has manual step sets the status to Paused like on other screenshots in the thread.


author: Dinara Tablina
body: Hello [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) ,

I've encountered the problem again and now I have the screenshot with these weird statuses.  
Do you have any idea what could be the reason?![statuses.png](https://community.atlassian.com/t5/image/serverpage/image-id/326022iBFFA7BA0196ED026/image-size/large?v=v2&px=999 "statuses.png")

comments: author: Poat
body: ... they got rid of the "unfilled circle" successful status.... [@Dinara Tablina](/t5/user/viewprofilepage/user-id/5495660)


author: Dinara Tablina
body: I know, but our developers don't need to run all steps every time they change the code. And it's very inconvenient to work with *Paused* statuses.


author: Patrik S
body: Hello [@Dinara Tablina](/t5/user/viewprofilepage/user-id/5495660) ,

and welcome to the Community!

Did you mean that all the pipelines executed in the past - which were already with the status *Successful/Failed* - got their status updated to *Paused*?

Would you mind sharing a screenshot from the Pipelines page where you see all pipelines paused from one of the affected repositories?

comments: author: Dinara Tablina
body: Hello, [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) ,

Yes, that's exactly what I meant: all my previous Successful or Failed pipelines got their status updated to Paused.  
Unfortunately, I can't share a screenshot now, because after a few hours the original statuses returned without any interference from me. But I'm wondering what could be causing of this behavior?


author: Patrik S
body: Hello [@Dinara Tablina](/t5/user/viewprofilepage/user-id/5495660) ,

That seems to have been just a temporary instability on the platform to get the actual build status, so I wouldn't expect it to happen again.

However, if you notice this same behavior in the future, please let us know so we can investigate further.


author: Dinara Tablina
body: Hello [@Patrik S](/t5/user/viewprofilepage/user-id/4603309) ,

Thank you for the reply!


author: Ruby
body: Same issue happens on 28/05/2024.


author: Alexander Grzesik
body: We have the same issue since yesterday. All pipelines with manual steps now show up as paused while before they where completed. I did not find anything that this is an intended change or a bug.  
For sure it is very annoying and confusing for the developers. We use manual tasks in all our pipelines to trigger release builds and now all look like something is wrong with the paused status. If this was an intended change it would be great to provide some documentation about it.


author: SMarkley
body: Can confirm. We are having the same issues. Just like you, we have some optional manual steps on all our build to be able to promote a build to various environments.

Now all our build show "Paused" except for the ones deployed all the way to Prod

If this is a platform change, please advise how I can mark a step in my yml to indicate a "completed" state


author: Poat
body: I'm brining my pitchfork to the party - all our builds show paused and this is confusing....

I could pause a build in the middle and it looks the same like completed builds w/ manual deploy :(


author: Bi Ling
body: I thought was something wrong with my pipelines flow. Now I've realized was a breaking change. I don't like it.


author: ginman86
body: fix this plz


author: Serhii Serhiienko
body: Also some manual steps are optional and up to situation if you need to run it or not. For example in our flow it's cache clean trigger, and in 99% is not runned, but up to developer if he need to run it or not.   
And that definetly not paused state.  
Or if you need to stick with status add some "optional step" field config on step level, so in this case if manual step not runned pipe is still successful.


Tags: bitbucket-cloud

cloud