Download artifact task failed when switching the branch in the Bamboo Specs linked repository

Issue Summary

This is reproducible on Data Center: Yes

The download artifact task failed when switching the branch in the Bamboo Specs linked repository

Steps to Reproduce

1. Created a Spec Repository with an artifact creation artifact download and automatic branch plan creation enabled.
2. Create a Linked Repository to and use the 'develop' branch and enable Bamboo Specs and scan
3. Create a branch named 'feature1' from the Repository and update the artifact name 
4. you will see the Branch plan has been created and built successfully
5. Now switch the branch in the linked repository to 'feature1'
6. Go to the Build plan, you will be able to see that 'Default branch' is now 'feature1'
7. Run the build plan

Expected Results

It should run successfully by generating the artifact and downloading the artifact it was pointing to.

Actual Results

The below build log can be seen in the download artifact job

error 30-Nov-2023 12:13:56 Build has not been started: java.lang.IllegalArgumentException: Unable to find an artifact definition for name: image_tag  

The below exception is thrown in the atlassian-bamboo.log file:

2023-11-30 12:13:56,333 WARN [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-64] [ChainExecutionManagerImpl] Build TEST-VRA-TES-6 has not been started
java.lang.RuntimeException: java.lang.IllegalArgumentException: Unable to find an artifact definition for name: image_tag
	at com.atlassian.bamboo.chains.ChainPluginSupportHelper.lambda$prepareRuntimeTaskData$0(ChainPluginSupportHelper.java:50) ~[atlassian-bamboo-core-9.3.4.jar:?]
	at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183) ~[?:?]
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195) ~[?:?]
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177) ~[?:?]
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177) ~[?:?]

Workaround

• push a  simple new change to the branch that is failing (Default Branch) and it will scan again and build will pass