Hello, I noticed this while using `org-resolve-clocks' when `org-clock-continuously' was set to true. Let's say I clock into "Task 1" at 12:00, and then at 12:30, I start working on "Task 2". Then, at 12:45, I notice that I forgot to clock out of "Task 1". No worries, org-mode has `org-resolve-clocks'! So, I invoke `org-resolve-clocks', keep 30 minutes, and then clock into "Task 2". However, when I clock in, the clock start time is 12:45, violating the promise that `org-clock-continuously' makes. This patch updates the variable `org-clock-out-time' when `org-clock-out' gets passed an `at-time', which fixes the issue I run into. The patch is attached. Is there anything else I need to do? Thanks, Benson