we have discovered an issue where running a Recurring Job manually does not set the last execution date, it remains N/A. This can be confusing because person could trigger the job thinking that the job has not been run yet, while it already has. This could cause some issues if the actual job being run does some critical stuff.
I noticed the same thing and it is a problem for me because I give the possibility to the user to run a recurrent job immediately, and I want him to display the statut of it.