Time worked not set as 00:00:00 on INSERT when requested via Service Catalog.Issue If you are using the time_worked field on the sc_req_item table if you submit a request via the service catalog the time_worked field is not auto-populated as 00:00:00. If you create a record manually it will be set. With a combination of using the property: glide.ui.timer.started (Timer doesn't start automatically) being set to false if you update the request item record it will record that update as a change of the file time_worked even though it went from 00:00:00 to 00:00:00 but since it was not inserted as 00:00:00 its recorded as NULL to 00:00:00. As it changes the value it will pass the condition (current.time_worked.changes();) If you wish to test you can: Set property to false: glide.ui.timer.started Add a BR in your instance for task using the condition: (current.time_worked.changes();) You will see it triggers on an update of the sc_req_item as the time_worked field changes. ResolutionThe workaround for this issue is to create a business rule which will populate the time_worked field on INSERT of sc_req_item. This will mean on the INSERT of the requested item the field will be 00:00:00 so with the timer not moving and the user saving the form it will not change the time_worked field and therefore will not pass the condition (current.time_worked.changes();) Please make sure you test this thoroughly in your instance and if you have any other logic with time_worked, but inserting a 0 time into the sc_req_item on INSERT should be fine.