My Yale YRD256 does not have scheduled jobs, so possibly it is there to check if the code has been added yet. What is the schedule set for (how often)? I assume when you tried to add the code that the command was sent, but the device probably did not respond so it is sort of stuck in that state with the requested change showing. LCM has mechanisms to retry but I am not totally sure how it works. I do not change my codes very often and it has worked good for my 4 locks in the house.
Also keep on mind every time you send a command to a z-wave lock it first tries the command straight away and there is maybe a 80% chance the lock will be sleeping (if you have not already woken it with other commands). So then if there is no response there is a 60 seconds long FLiRS beam which is sent out, and it will crush your mesh. Pretty much everything will be delayed while this beam is going out. The beams is to get the locks attention when it does its once every 60 check for a beam and makes it fully wake up to accept commands.
I would just focus on one lock at a time. First you may want to check some of the other locks and see if they have scheduled jobs. If there are a bunch with scheduled refreshes that might be crushing your mesh with wake up beams going out when the refreshes run. You can either disable the device or switch to the "Device" driver and use the command to remove scheduled jobs. Turn on debug logging for the lock being focused on and see that gives some more clues. LCM also has "moderate" logging mode which might help. Remember every time you send commands and it does not respond right away a beam will go out so if you keep pounding on it over and over its just going to saturate the mesh.
