> 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 Import & Configuration errors > This reference provides a comprehensive overview of meter import and configuration error codes, detailing their messages and offering suggested remedies for resolution. This reference provides a comprehensive overview of meter import and configuration error codes, detailing their messages and offering suggested remedies for resolution. Error code range: 70002217–70002260 | Code | Error Code | Error Message | Possible Remedy | | -------- | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | 70002217 | IMPORT_METER_MISSING_NAME | A meter name is required for import. | Provide a name in the import payload. | | 70002218 | IMPORT_METER_MISSING_LATEST_VERSION | The latest version is required for import. | Include the latestVersion field in the import payload. | | 70002219 | IMPORT_METER_MISSING_VERSIONS | At least one version is required for import. | Include at least one version entry in the import payload. | | 70002220 | IMPORT_METER_MISSING_METER_TYPE | A meter type is required. | Specify the meter type in the configuration. | | 70002221 | METER_DEFINITION_MISSING_PROCESSOR_ID | An ID is required for processor “\[Processor Name]”. | Assign a unique ID to the processor. | | 70002222 | METER_DEFINITION_MISSING_NAME | A name is required for processor “\[Processor Name]”. | Assign a name to the processor. | | 70002223 | METER_DEFINITION_MISSING_METADATA | Metadata is required for processor “\[Processor Name]”. | Configure the required metadata fields for the processor (varies by operator type). | | 70002224 | METER_DEFINITION_MISSING_PREDECESSORS | At least one predecessor is required for processor “\[Processor Name]”. | Connect at least one upstream source or processor. | | 70002225 | METER_DEFINITION_MISSING_PREDECESSOR_ID | A predecessor ID is required in processor “\[Processor Name]”. | Provide valid predecessor IDs in the processor's predecessors array. | | 70002226 | METER_TYPE_MISSING_EVENT_DEFINITION | An event definition is required. | Select or create an event definition for the meter type configuration. | | 70002227 | METER_TYPE_INVALID_DEFINITION | The event definition is invalid. Details: \[Error Details]. | Fix the event definition based on the error details and reassign it. | | 70002228 | METER_TYPE_MISSING_ACCOUNT_NUMBER_FIELD_MAPPING | A field mapping for Account Number is required. | Map the Account Number field in the meter type configuration to a field in your event definition. | | 70002229 | METER_TYPE_MISSING_CUMULATIVE_METHOD | A cumulative method is required for a Cumulative meter. | Select a cumulative method (e.g., “Sum”) in the meter type configuration. | | 70002230 | METER_TYPE_UNSUPPORTED_CUMULATIVE_METHOD | The cumulative method “\[Method Name]” is not supported. | Choose a supported cumulative method from the available options. | | 70002231 | METER_TYPE_MISSING_CUMULATIVE_PERIOD | A cumulative period is required. | Select a cumulative period (e.g., “Monthly”, “Daily”). | | 70002232 | METER_TYPE_UNSUPPORTED_CUMULATIVE_PERIOD | The cumulative period “\[Period]” is invalid. | Choose a supported cumulative period from the available options. | | 70002233 | METER_DEFINITION_DUPLICATED_PROCESSOR_ID | The processor ID “\[Processor ID]” is duplicated. | Rename one of the duplicate processors to use a unique ID. | | 70002234 | METER_DEFINITION_PREDECESSOR_ID_NOT_FOUND | The predecessor “\[Predecessor ID]” was not found in processor “\[Processor Name]”. | Correct the predecessor ID to reference an existing processor or source. | | 70002235 | METER_DEFINITION_MULTIPLE_STREAM_API_SOURCES | A meter supports at most one Streaming API source. | Remove extra Streaming API sources so only one remains. | | 70002236 | RUN_METER_MISSING_ID | A meter ID is required to run. | Provide the meter ID. | | 70002237 | RUN_METER_MISSING_NAME | A meter name is required to run. | Provide the meter name. | | 70002238 | RUN_METER_MISSING_VERSION | A meter version is required to run. | Provide the meter version. | | 70002239 | RUN_METER_MISSING_GLOBAL_ID | A global ID is required to run. | Provide the global ID. | | 70002240 | RUN_METER_MISSING_METER_DEFINITION | A meter definition is required to run. | Provide the meter definition in the run request. | | 70002241 | SOURCE_OPTION_MISSING_TEST_DATA | At least one test data source must be provided (sample file, local file, test data, or test data ID). | Provide test data via one of the supported methods: upload a sample file, provide inline test data, or reference an existing test data ID. | | 70002242 | SOURCE_OPTION_TEST_DATA_SIZE_TOO_LARGE | The test data exceeds the maximum allowed size of \[Maximum Size]. | Reduce the test data size. Use fewer rows or smaller payloads. | | 70002243 | RATING_SCHEDULE_UNSUPPORTED_BILLING_PERIOD | Only “Monthly” is currently supported as a billing period. | Set the billing period to “Monthly”. | | 70002244 | RATING_SCHEDULE_NO_BILLING_PERIOD_FOUND | No billing periods were found within the term \[Start Date] to \[End Date]. | Verify the subscription term dates. Ensure the term range is valid and spans at least one complete billing period. | | 70002245 | RATING_SCHEDULE_PIPELINE_NOT_FOUND | The rating pipeline “\[Pipeline Name]” was not found. | Verify the rating pipeline name or ID. | | 70002246 | RATING_SCHEDULE_PIPELINE_VERSION_NOT_FOUND | The rating pipeline “\[Pipeline Name]” version “\[Version Number]” was not found. | Verify the pipeline name and version number. | | 70002247 | DASHBOARD_TOO_MUCH_DATA | Too much data to display. Please select a smaller time range or a larger interval. | Narrow the time range or increase the aggregation interval to reduce the data volume. | | 70002248 | MERGE_SCHEMA_TYPE_MISMATCH | The upstream field “\[Field Name]” has conflicting types: “\[Type 1]” and “\[Type 2]”. Please ensure all upstream sources use the same type. | Update the upstream event definitions or map operators so the conflicting field uses the same type across all sources. | | 70002249 | EVENT_DEFINITION_INVALID_TYPE_TYPE | The “type” field of property “\[Property Name]” must be a string or an array. | Set the property's type to a single string (e.g., “string”) or an array of types (e.g., \[“null”, “string”]). | | 70002250 | EVENT_DEFINITION_INVALID_TYPE_VALUE | The “type” value for property “\[Property Name]” is invalid. Allowed types: string, number, integer, object, array, boolean, null. | Use one of the allowed type values. | | 70002251 | EVENT_DEFINITION_MULTIPLE_SCHEMA_EVENT_ID | Only one event ID field is allowed. Please remove duplicates. | Ensure only one field is marked as the event ID in the schema. | | 70002252 | LINEAGE_EMPTY_OPERATORS_IN_RUN_HISTORY | The run history “\[Run History ID]” has no operators defined for lineage. | Re-run the meter to generate lineage data. Ensure lineage is enabled for this meter. | | 70002253 | LINEAGE_TRACE_ID_DOES_NOT_MATCH_PIPELINE | The trace ID “\[Trace ID]” is invalid — it either does not exist or does not belong to this pipeline. | Verify the trace ID belongs to the current meter's run history. Use the correct trace ID from the lineage results. | | 70002254 | LINEAGE_NOT_SUPPORTED | Lineage is not enabled for run history “\[Run History ID]”. Please contact support to enable it, then re-run. | Contact support to enable lineage for your meter, then re-run it to generate lineage data. | | 70002255 | INVALID_OPERATOR_ID | The operator ID “\[Operator ID]” is invalid — it either does not exist or does not belong to this meter. | Verify the operator ID matches an operator in the current meter definition. | | 70002256 | METER_PINNED_COUNT_EXCEEDED | You can pin a maximum of \[Maximum Meter Count] meters. | Unpin an existing meter to make room. | | 70002257 | RUN_HISTORY_EXPORT_NO_DATA | There is no data available to export. | Run the meter first to generate data before exporting. | | 70002258 | EVENT_DEFINITION_UPDATE_UNSUPPORTED | This event definition does not support updates. | Create a new event definition instead of updating this one. | | 70002259 | CONCURRENT_QUERY_UNSUPPORTED | Another query is still in progress. Please wait for it to complete before starting a new one. | Wait for the current query to finish, then retry. |