Data & Operator errors
This reference provides comprehensive details on data and operator errors, including error codes, descriptions, and potential remedies.
Error code range: 70001200-70001299
| Code | Error Code | Error Message | Possible Remedy |
|---|---|---|---|
| 70001200 | DATA_VALIDATION_ALL_FIELDS | All expected fields are missing from the data. Please verify that you are ingesting the correct data format. | Verify the ingested data matches the event definition schema. Ensure you are sending data to the correct meter and that the payload structure (JSON keys, CSV columns) aligns with the configured event definition. |
| 70001201 | DATA_VALIDATION_ERROR | Data validation failed. Details: [Validation Details]. | Check the specific validation failure in the message. Common issues include incorrect data types, values out of range, or malformed fields. Fix the data at the source and re-ingest. |
| 70001202 | FS_GET_ETAG | Unable to retrieve the file identifier. | Verify that the source file exists and is accessible in S3 or the configured file system. Check IAM permissions and network connectivity. |
| 70001203 | LATE_DATA | This event arrived after the processing window closed and was not included. | Events must arrive within the configured processing window. Adjust the event timestamps at the source so they fall within the expected window, or reconfigure the meter's watermark/out-of-orderness settings to allow a wider tolerance. |
| 70001204 | DUPLICATE_EVENT | This event was skipped because it is a duplicate of a previously processed event. | No action required — deduplication is working as intended. If you believe this is incorrect, verify the event ID and timestamp are unique across your ingested events. Check deduplication settings (check type, specific fields) in the meter configuration. |
| 70001205 | SCRIPT_EXECUTE | Script execution failed. Details: [Error Details]. Please review your script for errors. | Open the script editor and review your script code. Test the script with sample data to reproduce the error. Common issues include undefined variables, type mismatches, or missing function definitions. |
| 70001209 | INVALID_EVENT_DATE | The event date “[Date]” is not valid. Please provide a correctly formatted date. | Ensure the event date field uses a supported date/time format (e.g., ISO 8601: 2024-01-15T10:30:00Z). Check that the event definition's event time field is correctly configured. |
| 70001210 | REQUIRED_COLUMN_MISSING | The required field “[Field Name]” is missing a value. Please ensure all required fields are populated. | Update the source data to include a value for the missing required field. Alternatively, review the event definition to confirm which fields are marked as required and adjust if needed. |
| 70001211 | REGISTER_AVRO_SCHEMA | Failed to register the Avro schema. Details: [Error Details]. | Validate your Avro schema for correctness. Ensure field names, types, and namespaces are valid. Retry the registration after fixing the schema. |
| 70001212 | PAYLOAD_MISSING | The event contains no payload data. Please ensure the event body is not empty. | Check the source system to ensure events are being sent with a non-empty body. Verify the event format and that the payload field is populated. |
| 70001213 | INVALID_COLUMN_DATA_TYPE | The value for field “[Field Name]” does not match the expected data type. | Check the event definition schema for the expected type of the field (string, number, integer, boolean). Fix the data at the source to send the correct type. |
| 70001214 | BLOOM_FILTER | Failed to create a deduplication filter. Details: [Error Details]. | This is typically a system-level issue. Retry the operation. If the error persists, contact support. |
| 70001215 | AVRO_UNKNOWN_DATA_TYPE | Unrecognized [Expected Value Type] value for field “[Field Name]”. The actual type is “[Actual Type]”. | Review the Avro schema and ensure the field type declarations match the actual data being sent. Update either the schema or the source data to align. |
| 70001216 | AVRO_ONLY_SUPPORT_2_UNION_TYPE | The field “[Field Name]” uses more than two union types, which is not supported. Please simplify the Avro union. | Simplify the Avro schema for this field to use at most two union types (e.g., ["null", "string"]). Complex union types are not supported. |
| 70001217 | SCRIPT_UPDATE_STATE | Failed to save script state. Details: [Error Details]. | Review the script's state management logic. Ensure the state key and value are valid and the state store is accessible. Retry the operation. |
| 70001218 | CSV_PARSE_NUMBER_ERROR | Could not parse column [Column Name]: the value [Value] is not a valid number. | Check the source CSV file for non-numeric values in numeric columns. Common issues include empty strings, text in number fields, or locale-specific number formats (e.g., commas as decimal separators). |
| 70001219 | INIT_WINDOW_OPERATOR_ERROR | The window operator could not be initialized. Please check your window configuration. | Review the aggregation operator's window settings — time field, granularity, timeout, and grouping. Ensure all required fields are configured and valid. |
| 70001220 | TSTORE_NOT_FOUND | We couldn't find the requested resource. | Verify that the requested resource exists and is correctly configured. Check the key or identifier passed to the operator. |
| 70001221 | PAYLOAD_METADATA_MISSING | Event metadata is missing. When creating a new event, please include the metadata from the original event. | If you use a script or map operator to create new events, ensure you copy the _metadata object from the original event into the new event. This metadata is required for downstream processing. |
| 70001222 | PAYLOAD_METADATA_INVALID | The event metadata is invalid. Please verify the metadata format. | Check that the event's _metadata object has not been corrupted or modified incorrectly in a script or map operator. Restore the original metadata format. |
| 70001223 | TSTORE_OPERATOR_STORE_NOT_FOUND | We couldn't find the requested resource. | The operator expects an associated key-value store that does not exist. This may indicate a configuration or deployment issue. Contact support if the problem persists. |
| 70001224 | FS_NDJSON_INVALID | The file is not in valid NDJSON (newline-delimited JSON) format. | Ensure each line in the file is a complete, valid JSON object. Verify there are no trailing commas, array wrappers, or multi-line JSON objects. |
| 70001225 | PAYLOAD_LENGTH_EXCEED | The payload size ([Payload Size]) exceeds the maximum allowed length ([Maximum Length]). Please reduce the payload size. | Reduce the size of individual event payloads. Consider removing unnecessary fields or splitting large events into smaller ones. |
| 70001226 | UNSUPPORTED_DATA_TYPE | The data type “[Data Type]” is not supported. | Check the event definition or operator configuration for the unsupported type. Replace it with a supported type (string, number, integer, boolean, object, array). |
| 70001227 | UNSUPPORTED_EVENT_DAY_TYPE | The event day data type “[Data Type]” is not supported. | Ensure the event day field uses a supported data type. Typically this should be a date or datetime string. |
| 70001228 | UNSUPPORTED_EVENT_TYPE | The event type “[Event Type]” is not supported. | Verify the event type matches one of the configured event definitions in your meter. Check for typos in the event type name. |
| 70001229 | ASYNC_EXECUTE_ERROR | An asynchronous operation failed. Details: [Error Details]. | Review the error details. This may indicate a timeout, network issue, or failure in an external service call. Retry the operation. If it persists, check external service availability. |
| 70001230 | CURRENCY_LOOKUP_MISSING_RATE_TYPE | A rate type is required for currency conversion. | Configure a rate type in the FX rate enrichment operator (e.g., "Daily", "Monthly"). |
| 70001231 | CURRENCY_LOOKUP_UNSUPPORTED_RATE_TYPE | The rate type “[Rate Type]” is not supported. | Use a supported rate type. Check the FX rate enrichment documentation for the list of supported rate types. |
| 70001232 | CURRENCY_LOOKUP_MISSING_FROM_ CURRENCY | A source currency is required for currency conversion. | Map the source currency field in the FX rate enrichment operator configuration. Ensure the event data includes the currency code. |
| 70001233 | CURRENCY_LOOKUP_ UNSUPPORTED_ FROM_CURRENCY | The source currency “[Source Currency]” is not supported. | Verify the currency code is a valid ISO 4217 currency code and is included in your synced currency rate data. |
| 70001234 | CURRENCY_LOOKUP_MISSING_TO_CURRENCY | A target currency is required for currency conversion. | Map the target currency field in the FX rate enrichment operator configuration. |
| 70001235 | CURRENCY_LOOKUP_UNSUPPORTED_TO_CURRENCY | The target currency “[Target Currency]” is not supported. | Verify the currency code is a valid ISO 4217 currency code and is included in your synced currency rate data. |
| 70001236 | CURRENCY_LOOKUP_MISSING_DATE_FIELD | A date field is required for currency conversion. | Map the date field in the FX rate enrichment operator. This field determines which day's exchange rate is used. |
| 70001237 | CURRENCY_LOOKUP_INVALID_DATE_FIELD | The date field “[Field Name]” is not valid for currency conversion. | Ensure the date field contains a valid date value in a supported format. |
| 70001238 | CURRENCY_LOOKUP_RATE_NOT_SYNCED | Currency rates are only available up to [Available Through Date]. Please use a date on or before that day. | The event's date is more recent than the latest synced FX rate. Either adjust the event date or wait for rates to be synced up to the required date. |
| 70001239 | CURRENCY_LOOKUP_RATE_NOT_AVAILABLE | The currency rate for [Currency/Date] is not yet available. Please try again later or contact support. | FX rates for this date have not been synced yet. Wait for the rates to become available, or contact support if the rate should already be present. |
| 70001240 | EVENT_PROCESS_FAILED | Event processing failed. Details: [Error Details]. | Review the specific error details. This is a general processing error. The root cause will be in the message. Fix the underlying issue and re-ingest the event. |
| 70001241 | BILLING_PERIOD_INVALID_FIELD_MAPPING | The billing period field mapping is invalid. Details: [Error Details]. | Review the billing period operator configuration and ensure all field mappings point to valid fields in the event data. |
| 70001242 | BILLING_PERIOD_MISSING_METADATA | Required billing period metadata is missing. Details: [Missing Metadata]. | Add the missing metadata to the billing period operator configuration. Required fields typically include subscription term start/end dates and billing period alignment. |
| 70001243 | BILLING_PERIOD_INVALID_BILL_CYCLE_DAY | The bill cycle day is invalid. Please provide a valid value. | Ensure the bill cycle day is a valid day number (1–31). This value must align with the subscription's billing configuration. |
| 70001244 | BILLING_PERIOD_NO_BILLING_PERIODS | No billing periods could be calculated. Please check your billing period configuration. | Verify that the subscription term dates, bill cycle day, and billing period alignment are configured correctly. Ensure the event date falls within the subscription term. |
| 70001245 | BILLING_PERIOD_START_DATE_DOES_NOT_ BELONG_TO_ANY_BILLING_PERIOD | The start date [Start Date] does not fall within any available billing period. | The event's start date is outside the calculated billing periods. Check that the subscription term covers this date and that billing period configuration is correct. |
| 70001246 | CUSTOM_WINDOW_ASSIGNER_START_DATE_MISSING | A start date is required for the custom window assigner. | Configure the start date field mapping in the custom window assigner operator. |
| 70001247 | CUSTOM_WINDOW_ASSIGNER_END_DATE_MISSING | An end date is required for the custom window assigner. | Configure the end date field mapping in the custom window assigner operator. |
| 70001248 | RATING_DRAWDOWN | A drawdown rating error occurred. Details: [Error Details]. | Review the drawdown configuration and ensure the fund, allocation rules, and associated charges are set up correctly. Check the error details for the specific cause. |
| 70001249 | INVALID_DATA_FORMAT | The data format is invalid. Details: [Error Details]. | Ensure the data conforms to the expected format (JSON, CSV, Avro, or Parquet) as configured in the source operator. |