Replacements with ${paramName} don't work in JobSchedulerManagedExecutableJob if the job is run outside the Managed Jobs environment

If ${paramName} replacements are configured for JobSchedulerManagedExecutableJob in the XML configuration, the Job Scheduler will try to replace these with environment variables already on startup.
As the configured parameters propably don't exist as environment variables,

{paramName} will be replaced by whitespace, leaving nothig for JobSchedulerManagedExecutableJob to replace.
(The {paramName}

parameters work in ManagedJobs because they are read from the database at runtime)