Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issues grabbing source from Bitbucket within AWS CodePipeline


When trying to Release a change from AWS CodePipeline (we have an existing Bitbucket integration), we intermittently get the following error message below.

"Action execution failed

[Bitbucket] Bitbucket returned an Internal Error exception. Please retry shortly. If the issue continues it may be reported on the Bitbucket status page at"
Usually retrying it gets past this issue and continues normally, but starting this afternoon around 1:30PM CST, we've been consistently receiving this message, even with multiple retries and on all of our other pipelines. We're not seeing an outage reported on
Here's the image pop-up we get for Action execution failed when we try to deploy our changes:

Screen Shot 2022-01-12 at 2.14.34 PM.png

11 answers

1 accepted

4 votes
Answer accepted
Mark C Atlassian Team Jan 12, 2022

Hi Everyone,

We received an update from our engineering team that the issue which is affecting the AWS CodePipeline integration feature is now resolved.

You can further check this incident here:

We apologize for the inconvenience this has caused you and your team.
If you need more help, please do let us know.

Mark C

It is happening again now. Haven't been able to pull from Bitbucket for some time now.

Like Andrew likes this

I can verify that when I change the repository settings to "Full Clone" it starts working again.

Same, happening again!

Like Andrew likes this

Hi @Mark C , seeing the same issue on my end. I just setup a CodePipeline with BitBucket source. The Source stage worked fine on first launch right after creating pipeline. Once I committed a new change in BitBucket, Source stage reran and failed. Reverted to original source code and same issue. I think its related to the webhook and will troubleshoot that next. Just want to confirm issue is still present.


Edit 1:

There's a few url redirects I've noticed when accessing target repo from project level in bitbucket webapp. It adds a redundant '/src/main/' to path. Not sure if this is new or has always existed but doesn't seem right.

Also, when I access the repo publicly with the https clone address provided, there's a pop up about credentials no longer needed (click OK) and lands me on what should be the repo address BUT without the redundant '/src/main/'. Reloading this page presents same error but once I add a '/' to end of url, shazam. It redirects through the redundant URL and correctly displays the repo.

Hope this helps. Hoping a fix is coming soon.

Hi, I'm experiencing the same issue just today. Please let me know if we have a way to resolve this on our end. 

Just to be clear we did not change anything in our code pipeline configuration. The  error bellow just suddenly popped out 

[Bitbucket] Bitbucket returned an Internal Error exception. Please retry shortly. If the issue continues it may be reported on the Bitbucket status page at

Same issue for me

Had the same issue since Jan 12, 2022 6:00 PM (UTC±0:00)

Have the same issue, which started a few hours ago. Full clone is not an acceptable workaround for me (using some codepipeline feature which does not work with full clone)

I was able to resolve this by ensuring the code pipeline source stage does a FullClone rather than the default "CodePipeline default"

Thanks, this fix the issue !

Like Frank DiRocco likes this

Having the same issue

I don't know if this will help the attlassian devs to debug this issue but codepipeline is using this URL to get the src for the branch and that results into "

"Resource not found

if you have your branch naming convention as feature/branch then bitbucket fails to redirect to URL like so

Hi, how do you know that? tks

Like Arturo Hurtado Romero likes this

Same issue here!!!

As of 16 January 2022, this bug still occur. Thanks to Frank DiRocco's advice, I solved it by setting code_build_clone_output as True in my CodeStar Connection.

Like this:

code_build_clone_output=True, # Bitbucket fix

We experience this issue today for all our branches with aws pipeline

Problem solve! nice!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events