On SQL 2016 server, I have a job that calls an SSIS package. This package is in the project in SSISDB and has options. One of these options is a string type, which is empty by default.
I completed the task with an empty value for this parameter and successfully completed.
Then I opened the properties of the job, went to the step that calls this package, and went into the configuration and gave this parameter a value.
I started the task again and successfully completed, and the parameter value received the expected effect on the results.
Now I want to change the task and return the parameter to an empty string. Repeating what I did above, I open the configuration and completely delete the parameter value.

When I try to save Job Step properties, I get an error message with a message in the subject line.
If I returned a non-empty value for this parameter, the job step can be saved.
When I first created the task, I was able to save it with an empty string for this value. It’s easy when I change the value to a non-empty string, start the task and then try to change it to empty, that I encountered this error.
I know that I can run the task to change the script, or delete and re-create the task step to get around this. I am not interested in knowing how to get around this problem.
: ?
- , ? .
EDIT: Aaron . . , , , .