@stalbert The script in question which is not found in the account while deploying, is it part of a suiteapp which is already in account? Or it exists in the project but sdf is not finding it? I am not 100% sure but if you have a dependency on a script which is part of another suiteapp, that might create the problem you are facing. If its part of your project then Sdf should resolve the dependency automatically and if this is not happening then its a bug. When you run add dependencies, it is adding the dependency in manifest? (In case your referenced script is in account and not in project)

It sounded to me like both are defined in the same project.

both were indeed in the same project and this is a customization project, not a SuiteApp. Also fyi this was deploying to a freshly refreshed sandbox, if that means anything.

@stalbert SDF should be able to manage the order of deployment, if your deploy xml is like this

<files>
   <path>~/FileCabinet/*</path>
 </files>
 <objects>
    <path>~/Objects/*</path>
 </objects>

To the best of my memory, If you have manually referenced the files then you have to place them in correct order. (i will double check this)

ah, I am manually selecting the entries (intentionally) in deploy.xml. I hope the order is handled in this case - we currently allow more files and/or objects in those folders than we want to deploy on any given customization. In other words, we want to be specific about what we're deploying and shy away from blind wilcard selection as shown above.