Thanks Michał - your steps to recreate the issue helped me track down the cause :-)
Essentially, any job containing 'initctl unset-env' or 'initctl unset-env --global' in any process stanza (post-stop, pre-start, etc) will trigger the issue when that job is restarted.
Note that the problem is not seen if the job is stopped and then started.
Thanks Michał - your steps to recreate the issue helped me track down the cause :-)
Essentially, any job containing 'initctl unset-env' or 'initctl unset-env --global' in any process stanza (post-stop, pre-start, etc) will trigger the issue when that job is restarted.
Note that the problem is not seen if the job is stopped and then started.