Hi Tony.

Sorry about that.  The problem has been fixed.  I've actually moved the update trigger (which updates the backend ever hour) from my own server to a remote server, so this should prevent this from happening again.

Cheers,

Gary.