@reneritchie @JamesFalconer @Miche11e looks like the issue is now resolved. Many thanks all!