What is the recommended interval for running Appian Health Check in a non-production environment?

Running the Appian Health Check at the recommended interval of every two weeks in a non-production environment is important to ensure that the system remains in an optimal state while taking into account continuous development and testing activities. This frequent check helps to identify potential issues early, particularly in manual testing or integration phases where changes are more likely to introduce new bugs or performance bottlenecks.

In a non-production setting, where updates and changes might be more dynamic compared to production, this bi-weekly interval allows for timely remediation actions before those issues could affect production deployments. It ensures that developers and teams can address configuration changes, system limits, and unexpected system behavior proactively.

Other options suggest infrequent intervals such as once a month or once a year, which may not provide sufficient oversight in an environment where frequent updates and tests are performed. Running a health check every week might be excessive for non-production, where things may not change that quickly, leading to unnecessary overhead. Therefore, the bi-weekly schedule strikes a balance between thorough checking and operational efficiency.