14th July 2018

Resolved

Issue is resolved. The problem was caused by the deployment of faulty configuration file of the Redis cache. We are sorry for inconvenience.