Orders table scheduled start/end fields being populated without anything scheduled

The smb.orders table has a scheduled_start and scheduled_end column that is getting filled with a time value that is the current time in GMT when the order is saved or deployed. This happens when you don't have a start or end date scheduled.

If you do, in fact, set a scheduled start or end date, the system will populate those fields with the date specified, not the current time.

If there are no scheduled start or end dates specified, these should be blank or null.

Note that the values the system actually uses for start and end dates comes from the json column anyway, not the scheduled_end or scheduled_start column.