> This page is for Docs. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://zuora.ferndocs.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server. # Meter Lifecycle errors > This reference provides a summary of meter lifecycle error codes, their messages, and suggested remedies for resolution. This reference provides a summary of meter lifecycle error codes, their messages, and suggested remedies for resolution. Error code range: 70002103–70002138 | Code | Error Code | Error Message | Possible Remedy | | -------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 70002103 | METER_NOT_EXISTING | The meter “\[Meter Name]” was not found. | Verify the meter ID or name. It may have been deleted or you may be looking at the wrong environment. | | 70002104 | METER_VERSION_NOT_EXISTING | The requested meter version was not found. | Verify the meter version number. List all versions of the meter to find the correct one. | | 70002105 | METER_ACTIVATE_ALREADY_ACTIVE | This meter is already active. | No action needed. The meter is already in the desired state. | | 70002106 | INVALID_METER_FILE | The uploaded meter file is invalid. Please check the configuration. | Ensure the meter file is a valid JSON file that conforms to the meter definition schema. Check for JSON syntax errors. | | 70002107 | INVALID_METER_TYPE | The meter type “\[Meter Type]” is not valid. | Use a supported meter type. Check the documentation for the list of valid meter types. | | 70002108 | INVALID_METER_VERSION_CONTENT | The meter definition content is invalid. Please check the configuration. | Review the meter definition for structural issues — missing operators, invalid connections, or incomplete configurations. Use the meter validation feature to identify specific problems. | | 70002109 | METER_VERSION_NOT_IDENTICAL | The version in the request body does not match the version in the URL. | Ensure the version number in your request body matches the version in the API path. | | 70002110 | IMPORT_PARAMETER_MISSING | Event definition names are required for import. | Provide event definition names when importing a meter. | | 70002111 | EVENT_DEFINITION_DETECT_FAILED | No event definition could be detected from the uploaded file. Please check the file format. | Ensure the uploaded file is in a supported format (JSON, CSV, Avro) and contains data from which a schema can be inferred. Try uploading a file with more representative sample data. | | 70002112 | EMPTY_METER_NAME | A meter name is required. | Provide a name for the meter. | | 70002113 | EMPTY_METER_VERSION | A meter version is required. | Provide a version number for the meter. | | 70002114 | INVALID_METER_VERSION | The meter version format is invalid. Please use the format “a.b.c” (for example, 1.0.0). | Use semantic versioning with three numeric components separated by dots (e.g., 1.0.0, 2.1.3). | | 70002115 | EMPTY_METER_TYPE_CONFIGURATIONS | Meter type configurations are required. | Provide the required meter type configurations including field mappings and settings. | | 70002116 | INVALID_METER_TYPE_TRANSITION | The meter type “\[Meter Type]” cannot be changed to Custom. | Certain meter type transitions are not allowed. Create a new meter with the desired type instead. | | 70002117 | CANNOT_DELETE_METER_WITH_VERSION_ACTIVATED | This meter cannot be deleted while it has active versions. Please deactivate all versions first. | Deactivate all active meter versions before deleting the meter. Navigate to each version and deactivate it. | | 70002118 | CANNOT_DELETE_ACTIVE_METER_VERSION | This meter version cannot be deleted while it is active. Please deactivate it first. | Deactivate the meter version before deleting it. | | 70002119 | CANNOT_DELETE_METER_VERSION_WHEN\_​NO_OTHER_EXISTS | This is the only meter version and cannot be deleted. Create another version before deleting this one. | Create a new version of the meter first, then delete the unwanted version. Alternatively, delete the entire meter. | | 70002120 | DUPLICATED_METER_VERSION | A meter with version “\[Version Number]” already exists. Please use a different version number. | Choose a unique version number that doesn't already exist for this meter. | | 70002121 | METER_DEACTIVATE_ALREADY_DEACTIVATED | This meter version is already deactivated. | No action needed. The meter version is already in the desired state. | | 70002122 | METER_VERSION_NOT_RUNNING | This meter version is not currently running. | The meter version must be running (activated and deployed) to perform the requested action. Activate and run the meter first. | | 70002123 | CANNOT_UPDATE_METER_VERSION_WHEN_ACTIVE | This meter version cannot be updated while it is active. Please deactivate it first. | Deactivate the meter version, make your changes, then reactivate it. | | 70002124 | CANNOT_UPDATE_METER_VERSION_WHEN\_​CONCURRENT_MODIFICATION | This meter is being updated by another session. Please try again shortly. | Wait a few moments and retry. Another user or process is currently modifying this meter. | | 70002125 | EMPTY_METER_ID | A meter ID is required. | Provide the meter ID in the request. | | 70002126 | EMPTY_METER_ENTITY_ID | An entity ID is required for the meter. | Provide the entity ID associated with the meter. | | 70002127 | METER_TYPE_EMPTY_FIELD_MAPPING_NAME | Every field mapping must have a name. Please fill in the blank mapping names. | Open the meter type configuration and ensure every field mapping entry has a name assigned. | | 70002128 | METER_TYPE_DUPLICATED_FIELD_MAPPING | Duplicate field mapping found for “\[Field Name]”. Please rename one of them. | Rename one of the duplicate field mappings to a unique name. | | 70002129 | METER_TYPE_FIELD_MAPPING_NOT_EXISTING\_ IN_EVENT_DEFINITION | The mapping field “\[Field Name]” does not exist in event definition “\[Event Definition Name]”. | Update the field mapping to reference a field that exists in the event definition, or add the missing field to the event definition. | | 70002130 | EVENT_DEFINITION_NOT_FOUND | The event definition “\[Event Definition Name]” was not found. | Verify the event definition ID. It may have been deleted or you may be referencing the wrong one. | | 70002131 | IMPORT_GOT_DUPLICATED_EVENT_NAME | The event definition name conflicts with an existing one. Please choose a different name. | Choose a unique name for the imported event definition. | | 70002132 | INVALID_EVENT_DEFINITION_FILE | The uploaded event definition file is invalid. | Ensure the event definition file is valid JSON that conforms to the expected schema format. | | 70002133 | DUPLICATED_EVENT_DEFINITION_NAME | This event definition name is already in use. Please choose a different name. | Choose a unique name for the event definition. | | 70002134 | METER_TYPE_FIELD_MAPPING_MUST_BE_NUMBER | The mapping field “\[Field Name]” must be of type number. | Update the event definition so this field has a number type, or choose a different numeric field for the mapping. | | 70002135 | METER_TYPE_EMPTY_FIELD_MAPPING | A field mapping is required for “\[Field Name]”. | Configure the required field mapping in the meter type settings. | | 70002136 | METER_TYPE_UNKNOWN_FIELD_MAPPINGS | Unknown field mapping name(s): \[Field Names]. | Remove the unrecognized field mappings or correct the names to match valid mapping fields. | | 70002137 | UNSUPPORTED_METER_QUERY_ORDER_FIELD | The sort field “\[Field Name]” is not supported. Please remove it from your query. | Remove the unsupported field from the orderBy clause of your query. | | 70002138 | UNSUPPORTED_NODE_TYPE_OR_OPERATOR_TYPE | The node type “\[Node Type]” with operator type “\[Operator Type]” is not supported. | Check the meter definition for an unsupported operator combination. Use a supported node and operator type. |