We have observed a potential issue with dataset refresh schedules when changing the Data Access mode.
When a dataset is configured with Automatic Caching, a reload schedule can be defined to refresh the data at specified intervals. However, if the Data Access setting is subsequently changed from Automatic Caching to Live, the previously configured reload schedule appears to remain active in the background.
As a result, the scheduled reload continues to run and may generate recurring failures, even though the dataset is now configured for Live access.
There is an additional usability issue: once the Data Access mode is changed to Live, the previously configured reload schedule is no longer visible from the dataset configuration. In our case, we observed recurring dataset reload failures in the Jobs page, but it was not immediately apparent that these failures were being triggered by a schedule created under the previous Automatic Caching configuration.
To identify and remove the schedule, we had to change the Data Access mode back to Automatic Caching, after which the existing schedule became visible and could be deleted.
Suggested enhancement: Automatically disable or remove the reload schedule when Data Access is changed from Automatic Caching to Live, ideally with a notification to the user. This would help prevent unnecessary refresh failures and make it easier for administrators and users to identify and manage active background schedules.
