A scheduled DataTransfer upload may not start as expected.
Example:
- Click Scheduled uploads
- Click Add
- Set Data source, Set time between 00:00 AM to 08:59 AM (In our example we are in the JST time zone)
- Set the next day as the Start date
- Click Save
![ScheduledUploadSettingScreen.png ScheduledUploadSettingScreen.png](https://community.qlik.com/t5/image/serverpage/image-id/67332i89C6CF45159EA6CB/image-size/medium?v=v2&px=400)
After saving, the next execution day is displayed for the day after tomorrow, skipping the originally scheduled date.
![SetNextExecutionDateIsNotExpectedDate.png SetNextExecutionDateIsNotExpectedDate.png](https://community.qlik.com/t5/image/serverpage/image-id/67333iA2161D04862682F8/image-size/large?v=v2&px=999)
Environment
- Qlik DataTransfer August 2021
- Qlik DataTransfer November 2021
Resolution
Known issue, DTB-50 reported to R&D.
Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support at support.qlik.com with the DTB-50 for reference.
Workaround:
If the time chosen has already passed server-side, QlikData Transfer may schedule the next execution wrongfully a day later.
To work around this, edit the task and set a later time.
Or execute the task manually on the missed day.
Cause
Product Defect ID: DTB-50
Related Content
Uploading on-premises data with Qlik DataTransfer ‒ Qlik Cloud