Skip to main content
Skip table of contents

Configuration Gap

A Configuration Gap is a mismatch between what's required for a setup and what's actually available. Examples include:

  • Testing a newer version (2.0) in an environment set up for an older one (1.1).

  • Not being able to recreate a problem in the testing environment because it doesn't match the production setup.

  • Booking a training environment that's unstable or slow.

The impact of these gaps can vary depending on the context and the environments involved. In production settings, such gaps are often treated as Incidents.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.