The backend is trying to load all the roles for all the users in the account, this is causing connection instability and 502 errors. Users are redirected to the "Oops something bad happened.." page and are not able to use the app. The work around is to refresh the page or close the browser tab and re-enter ZenQMS.

Due to unavailability of the system when this error occurs, we will be deploying this fix as soon as it is ready


This impacts any users who have experienced the "Oops something bad happened.." error page


This release is being managed through change control 301-54 You can download a copy of the first stages of the system release record, including the requirements and testing traceability matrix for release notes here: 2023.1p5 System Release Record 301-54 Release Notes. An entire release record will be available for review after the release is completed, in the auditor share account.


We expect 10 minutes of downtime.

Version Details

ZenQMS comprises a microservice architecture that breaks up large functions into smaller services. This reduces risk in the development and release process. As such this flagship release version is actually composed of the releases of the individual services components. It is entirely possible for a component service to not change versions in a release cycle even if other components do. Here is the summary for this release.


ZenQMS Release 2023.1p5 contains the following “FixVersions”.  We use FixVersion as an internal versioning scheme for our modules/services and maintain them in Jira.


AUTH 5.4

Updated Modules:


Unchanged Modules: 

  • Training
  • Documents
  • Audits
  • Issues
  • Change Control
  • Tasks
  • Settings
  • Administration
  • Daily Summary emails
  • Reports

Important Notes

  • This announcement plus the banner announcement in the application to ALL users is our formal announcement for the release.
  • Deployment (as always) is handled by the ZenQMS team
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.