Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Scheduled plans are not triggering after upgrade to 6.10.2

Hi since upgrading (6.10.2), we have noted that our weekly builds are not triggering.

We have approx 50 builds that are scheduled to run weekly each Sunday at 2am. Since upgrading we noted that these triggers are not firing.

Each build has 2 triggers

  • "Bitbucket Server repository triggered"
  • "Scheduled"


As part of the upgrade testing we fired them of manually and they run through to completion perfectly. We have also tested the Bitbucket server repository triggers. This are working also.


Not sure why but for the last 2 Sundays they have not triggered. I have not seen `System Errors` reported. What are my next steps to trouble shoot?





1 answer

1 accepted

1 vote
Answer accepted
Jimmy Seddon Community Leader Oct 06, 2019

Hi @Simon Hooper,

Have you looked in the looked at the atlassian-bamboo.log file in the 'logs' folder within the Bamboo_Home directory on your Bamboo server?  Specifically around the 2am time frame to see if any errors were reported when trying to run the scheduled trigger?

That would be the first place I would start.

I hope that helps!


Ok, we think we identified the issue. What happened at exactly 2am this Sunday? Daylight savings.

The server clock switched to 3am on the tick after 1:59:59am thus 2am never happened and the builds could not trigger. This was evident in the log file as the time stamps jumped 2am completely. Many thanks.

I dare say next Sunday will trigger fine.

Like # people like this
Jimmy Seddon Community Leader Oct 07, 2019

Hey Simon,

I'm glad you found a good lead on the answer.  To avoid that in the future is is possible to change the schedule time to either 1am or 3am?


I have put this recommendation to the team who owns these plans. Many thanks.

Like Jimmy Seddon likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

179 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you