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

Bamboo Clone Throws Plan Exists Error Every time


When I go through the clone process, it gives me the following error:

   Plan creation failed. Plan XXXXX-YYYYY already exists.

The plan did NOT, in fact, exist, but does now.  I can go on to modify it, but this happens EVERY time I clone.  Does this happen for anyone else?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 06, 2018

The Plan XXXXX-YYYYY may exist previously and then deleted.

Even though it is not shown in Bamboo, the data still exist in database and it will be cleared in scheduled job.

If the same key still does not work after a day, there might be error during scheduled deletion job. Check atlassian-bamboo.log to look for the deletion message to confirm if there is any error, example normal deletion log:

2018-09-06 22:55:33,229 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting 1 job(s) marked for deletion
2018-09-06 22:55:33,231 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting BAM-TEST-JOB1
2018-09-06 22:55:33,376 WARN [DelayedDeletionThread] [S3ArtifactHandler] S3 artifact handling won't work: bucket name is invalid: [null]
2018-09-06 22:55:33,393 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Skipping invalidation, plan is being deleted: BAM-TEST
2018-09-06 22:55:33,394 INFO [scheduler_Worker-3] [DeletionServiceHelper] Completed background deletion in 174.7 ms
2018-09-06 22:55:33,398 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting 1 stage(s) marked for deletion
2018-09-06 22:55:33,399 INFO [DelayedDeletionThread] [PlanManagerImpl] Removing 1 stage(s) for plan BAM-TEST
2018-09-06 22:55:33,406 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Skipping invalidation, plan is being deleted: BAM-TEST
2018-09-06 22:55:33,407 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-13] [DeletionServiceHelper] Completed background deletion in 12.94 ms
2018-09-06 22:55:33,413 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting 1 TopLevelPlan(s) and/or ChainBranch(es) marked for deletion
2018-09-06 22:55:33,413 INFO [DelayedDeletionThread] [DeletionServiceHelper] Deleting BAM-TEST
2018-09-06 22:55:33,439 INFO [DelayedDeletionThread] [AbstractQuartzTriggerActivator] Scheduler job not found, not deleted
2018-09-06 22:55:33,468 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Skipping invalidation, plan is being deleted: BAM-TEST
2018-09-06 22:55:33,490 INFO [DelayedDeletionThread] [ImmutablePlanCacheServiceImpl] Invalidating, plan is not in cache or is being loaded: BAM-TEST
2018-09-06 22:55:33,496 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-13] [DeletionServiceHelper] Completed background deletion in 89.54 ms

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events