When using aws thinkbox's Deadline, after manually modifying the properties of the job, the task is saved and re-entered the
queue and re-run, but the value of the environment variables set through the interface for the first time will be deleted and disappear.
For tasks submitted through the http://hostname:portnumber/api/jobs interface, the property is set in JobInfo = JSON object containing the Job Info, using the submit api. When you modify job properties, you can change the deadline interface, and the fields you modify include changing priority, changing the mempool, and manually modifying the silent mode (the variable value of one of the 7 tasks disappears), not all jobs have this problem, and some tasks have this problem.
When using aws thinkbox's Deadline, after manually modifying the properties of the job, the task is saved and re-entered the
queue and re-run, but the value of the environment variables set through the interface for the first time will be deleted and disappear.
For tasks submitted through the http://hostname:portnumber/api/jobs interface, the property is set in JobInfo = JSON object containing the Job Info, using the submit api. When you modify job properties, you can change the deadline interface, and the fields you modify include changing priority, changing the mempool, and manually modifying the silent mode (the variable value of one of the 7 tasks disappears), not all jobs have this problem, and some tasks have this problem.