Issue Summary

A deployment started by a scheduler trigger will not be able to download the artifacts if the last plan result is a specs update. The same will not happen if the deployment is manually triggered.

Steps to Reproduce

1. Configure a Bitbucket cloud specs plan that creates an artifact
2. Run a build in this plan
3. Create a deployment pointing to this plan, which will consume the artifact
4. Run a deployment manually to make sure the artifact is consumed
5. Run another build in the plan
6. Edit the specs configuration of the plan
7. Scan specs from the Bamboo repository configuration
8. Configure a scheduled trigger in the deployment for the next minute

Expected Results

The deployment will run and consume the artifacts from the last build

Actual Results

The deployment will fail with the following error in the build logs:

05-Apr-2019 18:45:00  Unable to download artifact Non required shared artifact: [artifact], pattern: [files]

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available