After deploying a new schedule management customization through our Azure DevOps pipeline, the schedule board auto-refresh functionality stopped working. The board only updates when manually refreshed, which is causing issues for our dispatchers who rely on real-time scheduling updates.
The deployment included updated web resources for custom schedule board views and some timer configuration changes. I’ve checked the schedule board config settings and the auto-refresh timer appears to be set correctly at 30 seconds, but it’s simply not triggering.
// Current timer config in web resource
var refreshTimer = {
interval: 30000,
enabled: true
};
The web resource deployment completed successfully according to the pipeline logs. Has anyone experienced auto-refresh issues after automated deployments of schedule board customizations?
Web resources need to be published after deployment for changes to take effect. Your pipeline might be deploying the files but not triggering the publish step. Check if your deployment script includes the PublishXml action or PublishAllCustomizations API call. Without publishing, the old cached version of the web resource remains active.
Also verify that your deployment didn’t accidentally overwrite the schedule board entity customizations. Auto-refresh depends on specific form events and OnLoad scripts. If your pipeline deployed a solution that included the schedule board form definition without the auto-refresh event handlers, that would break the functionality. Check the form XML to ensure the timer initialization code is still present in the OnLoad event.
Good point. I added a publish step to the pipeline and redeployed, but the auto-refresh still isn’t working. Could there be a browser caching issue? Our dispatchers are using the same browser sessions from before the deployment.
Browser caching is definitely a factor with web resource updates. But there’s also a server-side cache for schedule board configurations. Try clearing the D365 server cache through System administration > Inquiries > Database > SQL administration > Clear cache. Also check if your custom web resource is overriding the default auto-refresh event handlers - if the event binding is broken, the timer won’t trigger the refresh action even if it’s running.
I’ve seen this when deploying schedule board customizations. The issue is often that the web resource version number doesn’t get incremented during automated deployment. D365 uses the version number to determine if clients need to download the new resource. If the version stays the same, browsers keep using the cached old version. Your pipeline needs to automatically increment the web resource version in the customization XML before importing.