Is there a way to prevent the same technician from starting the same appointment that already has a log that's still In process ?

​@lorach 

Hi!There are settings under Service Order Types → Time Behavior that control what happens when the appointment is started, including options such as Start Logging for Services and Assigned Staff (If Any) and Start Logging for Unassigned Staff. Those settings can explain why logs are automatically created, but they do not appear intended to allow duplicate concurrent In Process logs for the same technician simply because Start was tapped twice.

The setting you are looking for is this one: “Start Appointment When Travel is Completed”:

This checkbox makes the system start the appointment automatically after the Arrive action. Probably, like other contributors mentioned, there are other automation settings on the service order type, that apart from starting the appointment will make the system register logs (Start Logging for Services and Assigned Staff (If Any) and Start Logging for Unassigned Staff), I advise you to turn those off too if you don’t want the Start action (start appointment) starts the logs for everyone. 

Hi ​@mohammadnawaz51 , thank you for your response.

Though these check boxes were turned off initially, because we want the users to start the log by themselves manually but the issue here is that, let's assume Technician A was assigned Appointment A, he will go ahead and start it at 11:41 which creates the intended first log, by users being users, for some reason he taps on start again without pausing his previous log, the system creates another log for same appointment A with a new start time of 11:42, so the appointment records two logs in process with two different start time, ideally I believe if technician A already has a registered log in process for appointment A, the system shouldn’t allow the user to registered another log unless the precious one is completed or paused.