Hi! Thanks for getting back to me! I can reproduce the issue with these trivial job files (can also provide in a zip if required, but there’s nothing fancy in them):
jobinfo1.txt:
Frames=0
Group=gpu
Name=Job1
Plugin=CommandLine
Pool=render
Priority=50
jobinfo2.txt
Frames=0
Group=gpu
Name=Job2
Plugin=CommandLine
Pool=render
Priority=50
plugininfo.txt
Arguments=/c echo hello
Executable=cmd.exe
Shell=default
ShellExecute=False
SingleFramesOnly=False
StartupDirectory=
batch.json
{
"Jobs": [
{
"JobInfoFilePath": "C:\\path\\to\\jobinfo1.txt",
"PluginInfoFilePath": "C:\\path\\to\\plugininfo.txt",
"JobDependencies": [],
"AuxiliaryFiles": []
},
{
"JobInfoFilePath": "C:\\path\\to\\jobinfo2.txt",
"PluginInfoFilePath": "C:\\path\\to\\plugininfo.txt",
"JobDependencies": [
"index://0"
],
"AuxiliaryFiles": []
}
]
}
Submitted via deadlinecommand.exe -submitmultiplejobsv2 -jsonfilepath path/to/batch.json. Note that there appears to be a bug with the command where the -jsonfilepath parameter must be explicitly spelt out, otherwise a “file was not found” error is returned, per this topic: Deadlinecommand SubmitMultipleJobsV2 Error - Deadline - AWS Thinkbox Discussion Forums (thinkboxsoftware.com)
We do indeed have a custom studio Event Plugin for managing licenses, etc.; while at first glance I can’t see anything in there that should affect job pending/queuing, I will need to do some further testing on that to confirm. Does submitting jobs via the V2 method trigger different events than the ‘V1’ way?
Here’s a screenshot of the Job History of a freshly submitted job exhibiting the issue:
