Fixing an SSIS package stuck in Created Execution

Occasionally, you may wind up with an SSIS package that is stuck in the status "Created Execution." In my case, the cause for this has been that new parameters have been added to the project, but a sql agent job has not been updated with values to set them. Then the sql agent job was kicked off and the job fails because it is missing the required values. This is even true when the values have been added to an environment and the sql agent job is setting them via the environment.

Whatever the cause, this is how you fix it:

1. In SSMS, under the Integration Services node, navigate down to the package and view the all executions report.
2. Click on the overview link for the one that is in the "created execution" status
3. Go to the "parameter values" table on the right and find the parameters with no value

 4. Connect to SSISDB and execute the following procedure for each missing parameter:

 5. Finally, kick off the execution with this stored proc: