Testing

This page covers common problems with metrics, tests, schedules, and results.

A test shows “error” or no results

Symptoms

• Tests run but return error.
• No metrics appear when defining conditions.

Likely causes

• No metrics-capable source is configured for the project.
• The metric name is incorrect or not present in the source.
• The source is disconnected or lacks permissions.

How to fix

• Confirm the project has a metrics-capable source such as Prometheus, Datadog, or Modulos Client.
• Verify the metric exists in the external system or is being pushed into Modulos.
• If you’re using Modulos Client, confirm MODULOS_API_KEY is set in the environment running the client.

Related: Testing Operating Model, Tests & Schedules

A test runs but the result is unexpected

Likely causes

• The threshold or operator is incorrect for the metric distribution.
• The metric is not scoped the way you expect, for example environment or model version.

How to fix

• Review the metric definition and any filters used by the source.
• Run the test manually and compare with the underlying metric in your monitoring system.

A schedule doesn’t seem to run

Likely causes

• The schedule is disabled.
• The test is not enabled.
• The source is unavailable during the schedule window.

How to fix

• Confirm the test status is enabled.
• Confirm the source is connected and producing recent data.
• If the issue persists, contact Support with the test name and last run timestamp.

When to contact Support

Include:

• project name
• test name
• metric name and source type
• a screenshot of the test and the latest result
• the approximate time the schedule should have run