Hi,
It looks like the following key=value pairs are unsupported by the DeadlineCommandBG.exe during submission of a custom plugin if initially set at the py submission script level as per the attached screen-grab.
Also, here’s a text copy dump of the “3dsmxs_job_info.job” local temp file as its being submitted:
Plugin=3dsMXS
Name=test
Comment=MXS Job
Department=
Pool=data
Group=none
Priority=50
TaskTimeoutMinutes=0
EnableAutoTimeout=False
ConcurrentTasks=1
LimitConcurrentTasksToNumberOfCpus=True
MachineLimit=0
Whitelist=
LimitGroups=
JobDependencies=
OnJobComplete=Nothing
Frames=0-0
ChunkSize=1
InterruptibleFlag=False
ReloadRenderer=False
SequentialJobFlag=False
SynchronizeAllAuxiliaryFiles=False
SuppressEvents=False
IgnoreFailedJobDetection=False
IgnoreFailedTaskDetection=False
SendJobErrorWarning=True
PreJobScript=
PostJobScript=
PreTaskScript=
PostTaskScript=
Tested in beta v6
Thanks,
Mike
Hey Mike,
These are the flags for those properties from our job submission documentation:
ForceReloadPlugin=[true/false]
Sequential=[true/false] *
Interruptible=[true/false]
*SequentialJob is also an accepted key name, but we don’t document it to avoid confusion.
Cheers,
Thanks Ryan that fixed it.
In Deadline v4.1, Sequential=[true/false] didn’t work and I had to use “SequentialJob”, but I guess that’s becuase its a change in v5 and not v4.1.
Also, the reason I got the naming convention wrong for those elements was because I just copied those names from the actual XML job info file, so I assumed they would be the same? Consistent?
The other settings all worked it was just these 3 names didn’t match their XML equivalent from the “Advanced” tab.
Thanks,
Mike
That’s why we always try to expose and document some sort of API to get/set this information. We never recommend looking at the repository “source” directly, because we can never guarantee that it won’t be changed. 
Cheers,
