Jump to content

Recommended Posts

Posted

@Lyonel @Joyce @JBasey some temporary heavy usage of a database resource meant it went into lockdown for a short while causing the issue you experienced. Whilst this is now sorted by freeing up the locked resource, we are looking to implement measures to prevent this scenario from reoccurring. Apologies for any inconveniences caused.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...