| Service | Status |
|---|
| Community access | ✅Available |
Summary
We have been experiencing an issue with the community which has meant that we have had to roll back an update. This has now been done and the community is available again
Most Recent Update – 14:03 25th November 2019
Hi everyone,
Today, we have had to revert a community update that one of our developers released earlier this morning. If you’ve had trouble loading any pages today, then it’ll be this update that’s the culprit. Between 11:15am and 14:20pm today, you wouldn’t have been able to read any of the community while logged into your account.
We’ve now reverted back to the code from Sunday evening, which should mean that everything’s back to normal. All the posts that you have made since then will still be there, but some images that you uploaded or avatars that you’ve changed this morning may be missing, and will need to be reuploaded.
We’re reviewing internally how this happened, as our testing and peer review procedures should prevent changes like this from having an adverse effect on members.
Again, we’d like to apologise for this having happened, and we’ll be learning from this to improve how we deploy code in future.
Thanks,
Dez
Update History
Most Recent Update – 14:03 25th November 2019
Hi everyone,
Today, we have had to revert a community update that one of our developers released earlier this morning. If you’ve had trouble loading any pages today, then it’ll be this update that’s the culprit. Between 11:15am and 14:20pm today, you wouldn’t have been able to read any of the community while logged into your account.
We’ve now reverted back to the code from Sunday evening, which should mean that everything’s back to normal. All the posts that you have made since then will still be there, but some images that you uploaded or avatars that you’ve changed this morning may be missing, and will need to be reuploaded.
We’re reviewing internally how this happened, as our testing and peer review procedures should prevent changes like this from having an adverse effect on members.
Again, we’d like to apologise for this having happened, and we’ll be learning from this to improve how we deploy code in future.
Thanks,
Dez
