Copy historical scores from PA to Benchmarks table job does not work if the System Administrator time zone is not set to GMT

The job should NOT be executed after going live with the Benchmark application. the historical collection and the copy job should be executed only when the KPIs are updated before going live and need to update the Bechmark dashboard before the Global scores are downloaded at 11th of each moth.

After executing the 'Benchmark Historical Data Collection' collection job, it is necessary to run 'Copy historical scores from PA to Benchmarks table' to reflect the updated scores on the benchmark dashboard.

'Copy historical scores from PA to Benchmarks table' will not work unless the

invalid start date in customer scores for indicator : ee6d8347536003000d620d0323dc34db

1- Execute 'Benchmark Historical Data Collection' collection job after making changes to the benchmark KPIs
2- Confirm the scores changed from Analytics Hub of the indicator(s)
3- Run the 'Copy historical scores from PA to Benchmarks table' job:
https://<instance_name>.service-now.com/nav_to.do?uri=sysauto_bm_script.do?sys_id=528c78655b551300514d484c11f91aeb
4- Observe errors from the localhost logs:
invalid start date in customer scores for indicator : ee6d8347536003000d620d0323dc34db
5- The Benchmark dashboard does not show the latest scores.

Expected results = The job should copy the PA scores to benchmark table so the Benchmark dashboard shows the updated scores.

The workaround is setting the time zone of System Administrator user as GMT and execute the job. The job will copy the PA scores and update the Benchmark dashboard.