> 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. # Event Definition errors > This reference provides a summary of event definition error codes, their messages, and suggested remedies for resolution. This reference provides a summary of event definition error codes, their messages, and suggested remedies for resolution. Error code range: 70002139–70002216 | Code | Error Code | Error Message | Possible Remedy | | -------- | ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 70002139 | EVENT_DEFINITION_EMPTY_NAME | An event definition name is required. | Provide a name for the event definition. | | 70002140 | EVENT_DEFINITION_EMPTY_SCHEMA | An event definition schema is required. | Define the schema with at least one property (field). | | 70002141 | EVENT_DEFINITION_EMPTY_TYPE | An event definition type is required. | Specify the type of the event definition. | | 70002142 | EVENT_DEFINITION_EMPTY_SCHEMA_PROPERTIES | The schema must contain at least one property. | Add at least one field (property) to the event definition schema. | | 70002143 | EVENT_DEFINITION_INVALID_SCHEMA_PROPERTIES_TYPE | Schema properties must be defined as a map (key-value pairs). | Ensure the properties field in the schema is a JSON object (map), not an array or primitive. | | 70002144 | EVENT_DEFINITION_INVALID_SCHEMA_PROPERTY_TYPE | Each schema property must be defined as a map (key-value pairs). | Ensure each property definition within the schema is a JSON object containing at least a type field. | | 70002145 | EVENT_DEFINITION_EMPTY_SCHEMA_PROPERTY_KEY | The schema property “\[Property Name]” is empty. Please provide a value. | Define the property with at least a type field. | | 70002146 | EVENT_DEFINITION_EMPTY_SCHEMA_PROPERTY_TYPE | The schema property “\[Property Name]” does not have a type defined. | Add a type field to the property definition (e.g., "type": "string"). | | 70002147 | EVENT_DEFINITION_MULTIPLE_SCHEMA_EVENT_TIME | Only one event time field is allowed. Please remove duplicates. | Review the schema and ensure only one field is marked as the event time field. Remove the extra designation(s). | | 70002148 | EVENT_DEFINITION_INVALID_SCHEMA_REQUIRED_TYPE | The “required” field in the schema must be a list. | Ensure the required field is a JSON array of field names (e.g., \["field1", "field2"]). | | 70002149 | EVENT_DEFINITION_EMPTY_FIELD_IN_SCHEMA_REQUIRED | The “required” list contains an empty entry. Please remove it or provide a value. | Remove empty strings from the required array. | | 70002150 | EVENT_DEFINITION_FIELD_IN_SCHEMA_REQUIRED\_​NOT_FOUND_IN_PROPERTIES | The required field “\[Field Name]” is not defined in the schema properties. | Either add the field to the schema properties or remove it from the required list. | | 70002151 | EVENT_DEFINITION_FIELD_IN_SCHEMA_REQUIRED\_​HAS_DUPLICATION | The “required” list contains duplicate entries. Please remove duplicates. | Remove duplicate field names from the required array. | | 70002152 | EVENT_DEFINITION_METER_VERSION_ID\_​SHOULD_BE_NULL_FOR_TENANT_SCOPE | Meter version ID should not be set for a tenant-scoped event definition. | Remove the meter version ID from the event definition if it is tenant-scoped. | | 70002153 | EVENT_DEFINITION_EMPTY_METER_VERSION_ID\_​FOR_METER_SCOPE | A meter version ID is required for a meter-scoped event definition. | Provide the associated meter version ID when creating a meter-scoped event definition. | | 70002154 | EVENT_DEFINITION_EMPTY_SAMPLE_FILE_ID | A sample file ID is required when testing with a sample file. | Upload a sample file first and use its ID when running a test. | | 70002155 | EVENT_DEFINITION_CANNOT_UPDATE\_ WHEN\_​REFERENCED_BY_ACTIVE_METERS | This event definition cannot be updated because it is referenced by active meters. Please deactivate the meters first. | Deactivate all meters that reference this event definition, make your changes, then reactivate the meters. | | 70002156 | EVENT_DEFINITION_CANNOT_DELETE\_ WHEN\_​REFERENCED_BY_METERS | This event definition cannot be deleted because it is referenced by meters. | Remove the event definition from all meters before deleting it. | | 70002157 | CSV_INVALID_DELIMITER_LENGTH | The CSV delimiter must be a single character. | Use a single-character delimiter for CSV (for example: comma , or tab \t). | | 70002158 | CSV_INVALID_FIRST_ROW | The first row number for CSV files must be greater than 0. | Set the first data row to 1 or higher. | | 70002159 | EVENT_DEFINITION_DETECT_INVALID_PARSING_DEPTH | The maximum parsing depth must be greater than 0. | Set the parsing depth to 1 or higher. | | 70002160 | SAMPLE_FILE_NOT_FOUND | The sample file “\[File Name]” was not found. | Verify the sample file ID. Re-upload the file if it has been deleted. | | 70002161 | EVENT_DEFINITION_CANNOT_UPDATE_WHEN\_​REFERENCED_BY_ACTIVE_METER | Event definition “\[Event Definition Name]” cannot be updated because it is referenced by active meter “\[Meter Name]” version “\[Version Number]”. | Deactivate meter "\[Meter Name]" version "\[Version Number]" before updating this event definition. | | 70002162 | EVENT_DEFINITION_CANNOT_DELETE_WHEN\_​REFERENCED_BY_METER | Event definition “\[Event Definition Name]” cannot be deleted because it is referenced by meter “\[Meter Name]” version “\[Version Number]”. | Remove the reference from meter "\[Meter Name]" version "\[Version Number]" or delete the meter version before deleting the event definition. | | 70002163 | EVENT_DEFINITION_UNSUPPORTED_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. | | 70002164 | EVENT_DEFINITION_INVALID_EXPORTED_CONTENT | The exported event definition content is invalid. | Re-export the event definition or manually correct the exported JSON. | | 70002165 | CSV_EMPTY_HAS_HEADER | The “hasHeader” option must be set to true for CSV files. | Enable the "hasHeader" option in the CSV file format settings. | | 70002166 | EMPTY_DATA_IN_FILE | No data was found in file “\[File Name]”. Please check that the file is not empty. | Upload a file that contains data rows. Verify the file is not empty or corrupted. | | 70002167 | MAXIMUM_FILE_LINES_EXCEEDED | The file exceeds the maximum of \[Maximum Line Count] lines. Please upload a smaller file. | Split your file into smaller chunks or reduce the number of rows to be within the limit. | | 70002168 | EMPTY_HEADER_IN_FILE | No header row was found in the file. Please check that the file is not empty and contains a header. | Ensure the file includes a header row as the first line with column names. | | 70002169 | EMPTY_RESOURCE_ID | A resource ID is required. | Include a resource ID in the request. | | 70002170 | CSV_COLUMN_SIZE_DOESNT_EQUAL_TO_HEADER_SIZE | The number of columns does not match the header on line \[Line Number]. Please check the CSV formatting. | Fix the CSV file at the indicated line. Ensure every data row has the same number of columns as the header. Check for unescaped delimiters or missing values. | | 70002171 | XML_NO_CHILD_NODES_UNDER_ROOT | No data nodes were found under the XML root element. Please refer to the XML example template. | Add data nodes under the XML root element. Refer to the provided XML template for the expected structure. | | 70002172 | XML_NO_CHILD_NODES_UNDER_NODE | No child nodes were found under data node “\[Node Name]”. Please refer to the XML example template. | Add child elements under the specified data node. | | 70002173 | TEST_DATA_NOT_FOUND | The test data “\[Test Data Name]” was not found. | Verify the test data ID. Re-create the test data if it was deleted. | | 70002174 | CANNOT_DELETE_TEST_DATA_WITH_SAMPLE_DATA | Test data that includes sample data cannot be deleted. | Remove the associated sample data first, then delete the test data. | | 70002175 | FILE_NOT_FOUND | The file “\[File Name]” was not found. | Verify the file ID. The file may have been deleted. Re-upload it if needed. | | 70002176 | EMPTY_RUN_HISTORY_QUERY_PARAM | A run history query parameter is required. | Include query parameters (e.g., meter ID, time range) when querying run history. | | 70002177 | UNSUPPORTED_RUN_HISTORY_QUERY_FIELD | The sort field “\[Field Name]” is not supported. Please remove it from your query. | Remove the unsupported field from the query's orderBy clause. | | 70002178 | RUN_HISTORY_NOT_FOUND | The run history “\[Run History ID]” was not found. | Verify the run history ID. It may belong to a different meter or may have been archived. | | 70002179 | AGGREGATION_FIELD_SCHEMA_DERIVATION_ERROR | The aggregation field “\[Field Name]” could not be derived from the upstream processors in “\[Processor Name]”. | Ensure the aggregation field name matches a field available from the upstream processors. Check the output schema of predecessor operators. | | 70002180 | SOURCE_FIELD_SCHEMA_DERIVATION_ERROR | The source field “\[Field Name]” could not be derived from the upstream processors in “\[Processor Name]”. | Ensure the source field name matches a field available from the upstream processors. Check the predecessor operator output schemas. | | 70002181 | EMPTY_METER_DEFINITION | A meter definition is required. | Provide a valid meter definition with at least one source, one processor, and one target. | | 70002182 | PROCESSOR_NOT_FOUND_IN_METER_DEFINITION | The processor “\[Processor Name]” was not found in the meter definition. | Verify the processor ID exists in the meter definition. Check for typos. | | 70002183 | PREDECESSORS_NOT_FOUND | The processor “\[Processor Name]” has no connected upstream processors. | Connect at least one upstream processor (or source) to this processor. | | 70002184 | SCHEMA_DERIVATION_ERROR | Unable to derive the schema for processor “\[Processor Name]”. | Review the processor's configuration and its upstream connections. Ensure predecessor operators have valid output schemas. | | 70002185 | DANGLING_SOURCE | The source “\[Source Name]” is not connected to any processor. Please connect it to at least one processor. | Draw a connection from this source to at least one downstream processor in the meter definition. | | 70002186 | SOURCE_HAS_NO_EVENT_DEFINITION_ID | The source “\[Source Name]” does not have an event definition assigned. | Assign an event definition to this source operator. | | 70002187 | SOURCE_HAS_EMPTY_METADATA | The source “\[Source Name]” has no metadata configured. | Configure the required metadata (connection, path, format, etc.) for the source operator. | | 70002188 | SOURCE_HAS_INVALID_EVENT_DEFINITION_ID | The source “\[Source Name]” has an invalid event definition ID: “\[Event Definition ID]”. | Correct the event definition ID or assign a valid event definition. | | 70002189 | EVENT_DEFINITION_NOT_FOUND_IN_SOURCE | The event definition “\[Event Definition Name]” was not found in source “\[Source Name]”. | Assign a valid, existing event definition to the source. | | 70002190 | SOURCE_HAS_EMPTY_EVENT_DEFINITION | The event definition “\[Event Definition Name]” in source “\[Source Name]” is empty. | Provide a complete event definition with a valid schema. | | 70002191 | SNOWFLAKE_UNSUPPORTED_AUTH_METHOD | The Snowflake authentication method “\[Authentication Method]” is not supported. | Use a supported authentication method (e.g., key-pair authentication). | | 70002192 | SNOWFLAKE_UNSUPPORTED_UNLOAD_FILE_FORMAT | The Snowflake unload file format “\[File Format]” is not supported. | Use a supported unload format (e.g., CSV, JSON, Parquet). | | 70002193 | SNOWFLAKE_SQL_ERROR | A Snowflake SQL error occurred. Details: \[Error Details]. | Review the SQL query for syntax errors. Check table/view names, column references, and permissions. | | 70002194 | NOT_ALL_TASK_IDS_ARE_SOURCE_OR_TARGET | All specified task IDs must be of type Source or Target. | Ensure you only reference source or target operator IDs in this context. | | 70002195 | NO_SPECIFIC_TASK_ID_IN_METER | No matching task ID was found in the meter. | Verify the task ID and ensure it exists in the meter definition. | | 70002196 | INVALID_FILE_NAME | The file name “\[File Name]” is invalid. Please include a file extension (for example, .csv or .json). | Rename the file to include a valid extension. | | 70002197 | DEPENDENCY_CIRCLE_IN_METER_DEFINITION | A circular dependency was detected at processor “\[Processor Name]”. Please review the processor connections. | Break the circular dependency by rearranging the processor connections so data flows in one direction without loops. | | 70002198 | ON_DEMAND_QUERY_UNSUPPORTED_SOURCE_TYPE | The source type “\[Source Type]” is not supported for on-demand queries. | Use a supported source type for on-demand queries. | | 70002199 | ON_DEMAND_QUERY_SOURCE_FOLDER_NOT_EXISTING | The source data “\[Source Data Name]” was not found. | Verify the source data path exists and contains data. | | 70002200 | SNOWFLAKE_ROLE_NOT_AUTHORIZED | The Snowflake role “\[Role Name]” was not found or you do not have access to it. | Verify the Snowflake role name and ensure your Snowflake user has been granted this role. | | 70002201 | SNOWFLAKE_DATABASE_NOT_AUTHORIZED | The Snowflake database “\[Database Name]” was not found or you do not have access to it. | Verify the database name and ensure the configured Snowflake role has access to it. | | 70002202 | SNOWFLAKE_SCHEMA_NOT_AUTHORIZED | The Snowflake schema “\[Schema Name]” was not found or you do not have access to it. | Verify the schema name and ensure the configured Snowflake role has access. | | 70002203 | SNOWFLAKE_TABLE_NOT_AUTHORIZED | The Snowflake table “\[Table Name]” was not found or you do not have access to it. | Verify the table name and ensure the configured Snowflake role has SELECT privileges. | | 70002204 | SNOWFLAKE_DUPLICATED_TABLE | Multiple Snowflake tables named “\[Table Name]” exist. Please specify the database and schema. | Fully qualify the table name with database and schema (e.g., my_db.my_schema.my_table). | | 70002205 | SNOWFLAKE_WAREHOUSE_NOT_AUTHORIZED | The Snowflake warehouse “\[Warehouse Name]” was not found or you do not have access to it. | Verify the warehouse name and ensure the Snowflake role has USAGE privileges on it. | | 70002206 | UNSUPPORTED_METER_QUERY_FIELD | The query field “\[Field Name]” is not supported. | Remove the unsupported field from your query. | | 70002207 | UNSUPPORTED_METER_SOURCE_TYPE | The source type “\[Source Type]” is not supported. | Use a supported source type. Check the documentation for the list of available source types. | | 70002208 | EVENT_DEFINITION_INVALID_FIELD_NAME | The event definition field name “\[Field Name]” is invalid. | Use valid characters in field names (letters, numbers, underscores). Avoid special characters and spaces. | | 70002209 | FIELD_VALUE_WRONG_TYPE | The value of field “\[Field Name]” must be a list. | Provide the field value as a JSON array. | | 70002210 | FIELD_VALUE_TYPE_SHOULD_BE_NUMBER | The condition field “\[Field Name]” must have a numeric value. | Provide a numeric value for this condition field. | | 70002211 | INVALID_OUTPUT_SCHEMA | Invalid output schema: no properties defined for “\[Property Name]” in node “\[Node Name]”. | Add properties to the output schema for this operator. | | 70002212 | UNSUPPORTED_SCHEMA_DATA_TYPE | The schema data type “\[Data Type]” is not supported. | Use a supported data type: string, number, integer, boolean, object, array. | | 70002213 | UNSUPPORTED_SCHEMA_SAMPLE_FORMAT | The schema sample format “\[Format]” is not supported. | Use a supported sample file format (JSON, CSV, Avro). | | 70002214 | MISSING_SOURCE_OPTIONS | Source options are required. | Provide source options (test data, sample file, etc.) when running or testing the meter. | | 70002215 | SCHEMA_DERIVATION_MISSING_TASK_ID | A task ID is required for schema derivation. | Provide the task (operator) ID for which to derive the schema. | | 70002216 | SCHEMA_DERIVATION_MISSING_METER_DEFINITION | A meter definition is required for schema derivation. | Provide the meter definition when requesting schema derivation. |