I was using this approach, but instead of renaming the job I created a new one and borrowed the step from the original job. I did this because I wanted to control multiple report refreshes from a single job. I deleted the "guid" named job. However, I noticed that the next day the "guid" named job was back.

(1) It would have been nice if Microsoft would give us the ability to name the job during the "configuration" creation.

(2) If the report execution configuration is turned off, the event behind the original job and now copied into the new one goes away. Micosoft could have done a better job here.