@WestHost Thanks for checking in. Alas no, we've not been able to pinpoint the resource issue. I'm all out of ideas now I'm afraid. :-(