---
title: Continuous Testing and CI/CD Troubleshooting
description: >-
  Learn about Continuous Testing and CI/CD concepts and troubleshoot common
  errors.
breadcrumbs: Docs > Continuous Testing > Continuous Testing and CI/CD Troubleshooting
---

# Continuous Testing and CI/CD Troubleshooting

## Overview{% #overview %}

This page provides information to help you troubleshoot issues with Continuous Testing and CI/CD. If you need additional help, contact [Datadog support](https://docs.datadoghq.com/help/).

## Terminology{% #terminology %}

{% dl %}

{% dt %}
CI batch
{% /dt %}

{% dd %}
The group of Continuous Testing tests triggered through a continuous integration or continuous delivery (CI/CD) pipeline or the [Datadog Synthetic Monitoring API](https://docs.datadoghq.com/api/latest/synthetics/#trigger-tests-from-cicd-pipelines).
{% /dd %}

{% dt %}
Test run
{% /dt %}

{% dd %}
A single run of a Continuous Testing test, which can be an [API](https://docs.datadoghq.com/synthetics/api_tests/) or [browser test](https://docs.datadoghq.com/synthetics/browser_tests/?tab=requestoptions). If you have configured retries, they count as individual test runs. For example, a test with two retries can have up to three associated test runs.
{% /dd %}

{% dt %}
Parallel test
{% /dt %}

{% dd %}
A Continuous Testing test that is run at the same time as another Continuous Testing test in your CI/CD pipeline. To set how many tests you would like to run in parallel, configure parallelization on the [Continuous Testing Settings page](https://docs.datadoghq.com/continuous_testing/settings).
{% /dd %}

{% dt %}
Batch timeout
{% /dt %}

{% dd %}
A batch timeout occurs when your batch does not complete within a reasonable time based on the [polling timeout](https://docs.datadoghq.com/continuous_testing/cicd_integrations/configuration/?tab=npm#global-configuration-file-options) set in your configuration file.
{% /dd %}

{% dt %}
Execution rule
{% /dt %}

{% dd %}
An [execution rule](https://docs.datadoghq.com/continuous_testing/cicd_integrations/configuration/?tab=npm#test-files) defines the impact of a test failure on a CI/CD pipeline from most to least impactful: `skipped`, `non_blocking`, and `blocking`. These options are weighted and default to the most impactful. If your test is configured as `skipped` in the UI and `blocking` in the configuration file, it is skipped during the test run.You can set the execution rule in your tests' properties, global configuration file, or an individual test's override file.
{% /dd %}

{% /dl %}

## Results Explorer{% #results-explorer %}

### CI metadata does not appear{% #ci-metadata-does-not-appear %}

Check whether you are using API endpoints to trigger your CI/CD test runs. In order to populate the Synthetic Monitoring & Continuous Testing Results Explorer with CI metadata, you must use one of Datadog's [native integrations](https://docs.datadoghq.com/continuous_testing/cicd_integrations), or the [NPM package](https://docs.datadoghq.com/continuous_testing/cicd_integrations#use-the-cli).

## Within your CI/CD pipeline{% #within-your-cicd-pipeline %}

### My tests are timing out in my CI pipeline{% #my-tests-are-timing-out-in-my-ci-pipeline %}

The first thing to check is which failure mode flags you are passing in your [global configuration file](https://docs.datadoghq.com/continuous_testing/cicd_integrations/configuration/?tab=npm#global-configuration-file-options). For CI runs that contain multiple tests, some tests are queued based on the parallelization setting defined on the [Continuous Testing Settings page](https://docs.datadoghq.com/continuous_testing/settings). You may need to adapt both your configuration and parallelization based on your organizational needs.

## Synthetics monitors{% #synthetics-monitors %}

The CI does not trigger Synthetics monitors or incorporate them into monitor evaluations; however, failing runs will result in the CI showing a red status.

## Further reading{% #further-reading %}

- [Learn how to configure Continuous Testing and CI/CD](https://docs.datadoghq.com/synthetics/cicd_integrations/configuration)
- [Best practices for continuous testing with Datadog](https://www.datadoghq.com/blog/best-practices-datadog-continuous-testing/)