Spurious 'trigger changed' messages generated by scheduled task provider

The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:

notice: /Stage[main]/Schedtask/Scheduled_task[restart_some_service]/trigger: trigger changed '{'every' => '1', 'on' => ['sun'], 'schedule' => 'weekly', 'start_date' => '2012-10-22', 'start_time' => '01:00'}' to '[{'day_of_week' => ['sun'], 'schedule' => 'weekly', 'start_time' => '01:00'}]'

The resource associated with the task looks like this:

  scheduled_task { 'restart_some_service':

    ensure  => present,

    enabled => true,

    command => 'c:\windows\restart_some_service.bat',

    user    => 'SYSTEM',

    trigger => {

      schedule    => weekly,

      day_of_week => [sun],

      start_time  => '01:00',

    },

    require => File['restart_some_service.bat'],

  }

This seems to be some kind of artifact of date conversion/formatting or something. While Puppet reports a change, examining the history tab for the task shows no changes aside from the initial creation of the task and subsequent 'real' changes which were initiated by actually modifying the resource. The notices will be generated regardless of whether there is a real change to report.