App not in a state where new builds are allowed

The Veracode platform design allows only one-at-a-time ongoing scan in progress within an application or a sandbox. The ongoing scan can be in prescan, scan, or even an incomplete failed state.  If there is more than one sandbox within an application, each sandbox can have a single scan at a time, and the application policy can also have a single scan at a time. The ongoing single scan can be static or dynamic.

In case you want to override the "App not in a state where new builds are allowed" principle state, you may choose one of these actions:
* Wait for the ongoing scan to be completed and published
* delete the scan (build)
* create a new sandbox within the same application and submit the scan into it. Note that a sandbox scan can be promoted to an application policy scan subsequently. 

The " App not in a state where new builds are allowed" error is not included in the activity log for an application from the application page or the Scans page (https://docs.veracode.com/r/c_viewing_detailed_scan_activity) as it is an API returned error that was unsuccessful and did not reach the Veracode platform or changed any state of the application. 

Refer also to the Help Center, Troubleshooting IDE Integrations   https://docs.veracode.com/r/Troubleshooting_Veracode_APIs_and_Wrappers page .

Topics (1)

Related Articles

Related Topics

    Ask the Community

    Get answers, share a use case, discuss your favorite features, or get input from the Community.