--- sourceDocument: Brazil Telecommunications, Media, and Technology sourceDocumentLink: https://www.servicenow.com/docs/r/telecom-media-technology Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Telecommunications, Media, and Technology ft:clusterId : - telmt bundleId : - telmt workflow : - Customer and Industry --- # Error messages # Service Test Management error messages {#ariaid-title1} Release version: Brazil Updated October 13, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Find the cause of a Service Test Management error message and the action that resolves it. ## Test group messages {#stm-error-messages__stm-errors-group} {#stm-error-messages__table_stm_errors_group__entry__2} | Message | Cause and resolution | |-|-| | No test definition is associated with this test group. You can not publish it. | A manual test group needs at least one test definition. Add a test definition, or change the execution type to Automated before you publish. See [Map test definitions to a test group](https://www.servicenow.com/docs/cgJW3dItjo_KevFWgLa6rg "Map test definitions to a draft test group and set the order in which they run."). | | Test group state must be in Draft state. | You can change the definition mappings of a test group only while the group is in the Draft state. | | Test group state must be in Published state. | Publish the test group before you relate it to a specification or a product model. | | A record with the same Test Definition and Test Group already exists. Please provide unique values. | The test definition is already mapped to this test group. A definition can be mapped to a group only once. | | You cannot update the 'Execution Type' field when the state is 'Published'. | Choose the execution type before you publish the test group. | [Table 1. Test group messages] {#stm-error-messages__table_stm_errors_group} ## Relationship messages {#stm-error-messages__stm-errors-relationship} {#stm-error-messages__table_stm_errors_rel__entry__2} | Message | Cause and resolution | |-|-| | Provide exactly one of Specification or Product Model. | Fill in one of the two fields, not both and not neither. | | Conditions cannot be set with Product Model; condition scoping is specification-driven. | Use a specification if you want to set conditions. See [Define conditions for a test group relationship](https://www.servicenow.com/docs/gV4fHKmx0COBFDK1NtBBZw "Add conditions to the relationship between a specification and a test group so that the test group applies only to product inventory records that meet the conditions."). | | Product Model must be populated. | Without the Product Model plugin, a test group relationship needs a product model. | | A record with the same Product Model and Test Group already exists. Please provide unique values. | The test group already has a relationship for that product model. | | Invalid update: this relationship creates a cyclical relationship between test definitions. | Choose a related test definition that doesn't lead back to this one. | [Table 2. Relationship messages] {#stm-error-messages__table_stm_errors_rel} ## Test definition messages {#stm-error-messages__stm-errors-definition} {#stm-error-messages__table_stm_errors_def__entry__2} | Message | Cause and resolution | |-|-| | Related Test Definition can only be added or modified when the test definition is not empty and state is in the draft state. | You can change relationships, test measure definitions, threshold rules, and measure consequences only while the test definition is in the Draft state. | | This test definition is used in published test definitions. You cannot retire it. | Retirement is blocked while a published test definition uses this one as a related test definition. Remove the relationship first. | | The following test definition(s) are used in published test definitions. So these test def(s) won't be retired. | You retired several test definitions from a list, and some are the related definition of a published test definition. The system retires the others and skips these. Remove the relationship from the published definition to retire them. | | Changing the state from {0} to {1} is not permitted. | A test definition can't move back to an earlier state. See [Test definitions in Service Test Management](https://www.servicenow.com/docs/t4STlHAHnKqPu1DgzNFPWQ "A test definition specifies the parameters, metrics, and threshold rules for a service test. Use test definitions to identify the root cause of service problems across service types, product models, and inventory."). | | If Comparator Exact is true Target Exact must be populated. | One of several comparison messages on a threshold rule. Check the comparison rules in [Threshold Rule form fields](https://www.servicenow.com/docs/vhMhMGjLB23XT8QqdP9uuw "Review the fields on the Threshold Rule form and the rules that govern which comparators and targets you can combine."). | [Table 3. Test definition messages] {#stm-error-messages__table_stm_errors_def} ## Other behavior {#stm-error-messages__stm-errors-other} A test definition doesn't appear when you select one for a test run : A test run can reference only a published test definition. Publish the definition first. For more information, see [Publish a test definition](https://www.servicenow.com/docs/_FYV8ozl2bda8hEPLj5KGQ "Publish a test definition in the Service Test Management application so that test runs can reference it and your teams see only approved tests."). Archiving skips some test definitions and names them in a message : A test definition that a published definition uses as a related definition isn't archived. For more information, see [Archive test definitions](https://www.servicenow.com/docs/SHydCHfg8mYToTYufmWqiw "Archive retired test definitions in the Service Test Management application to take them out of the working list.").