Referenz der Fehlercodes¶

`E001` — Invalid Dataset¶

Dataset '{dataset}' is not supported{entity_clause}. Use a supported 2-letter dataset code (e.g., US) or remove the dataset attribute to use the default.

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E002` — Invalid Locale¶

Locale {locale_label} is not supported{entity_clause}. {guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E003` — Datetime Conversion Failed¶

Failed to convert datetime value of <{element_tag}> '{name}'{format_clause}: {cause}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E004` — Entity Init Failed¶

Can't create entity '{entity}': {cause}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E005` — Rule Eval Failed¶

Failed to evaluate {kind} '{expr}' for <{element_tag}>{descriptor}{cause_clause}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E006` — Invalid Source¶

Invalid source: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E007` — Export Config¶

Invalid exporter configuration: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E008` — Include Error¶

Include failed: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E009` — Generator Config¶

Invalid generator configuration: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E010` — Condition Eval Failed¶

Invalid : {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E011` — Parser Validation¶

Descriptor validation error: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E012` — Client Config¶

Invalid client configuration: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E013` — Task Config¶

Invalid task configuration: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E014` — Operation Error¶

Operation failed: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`E015` — Runtime Config¶

Invalid runtime configuration: {issue}{guidance}

Warum: A runtime error was classified in this top-level error category.

Lösung: Inspect the nested issue code and descriptor context for the actionable resolution.

`I101` — Source File Not Found¶

Source file '{name}' not found in task workspace

Warum: The source file path resolved under the task workspace but the file does not exist.

Lösung: Place the file under the descriptor directory or update the source path.

`I102` — Source Invalid CSV¶

Invalid CSV in '{name}'

Warum: The CSV file content is malformed or cannot be parsed.

Lösung: Fix CSV syntax, delimiter, and quoting, then retry.

`I103` — Source Invalid CSV Header¶

Invalid CSV in '{name}'. CSV sources must include a header row

Warum: The CSV source is missing a header row required for column mapping.

Lösung: Add a header row to the CSV source and retry.

`I104` — Source Invalid JSON¶

Invalid JSON in '{name}'

Warum: The JSON file content is malformed or cannot be parsed.

Lösung: Fix JSON syntax and ensure the file is valid JSON.

`I105` — Source Invalid XML¶

Invalid XML in '{name}'

Warum: The XML file content is malformed or cannot be parsed.

Lösung: Fix XML syntax and ensure the file is well-formed.

`I106` — Source Invalid NDJSON¶

Invalid NDJSON in '{name}'

Warum: The NDJSON content contains invalid JSON lines.

Lösung: Ensure each line is a valid JSON object and retry.

`I107` — Source JSON Root Invalid¶

JSON file '{name}' must contain a list of objects or a dictionary

Warum: The JSON root value is not a list of objects or a dictionary.

Lösung: Use a JSON array of objects or a dictionary at the root.

`I108` — Source XML Root Invalid¶

XML file '{name}' must contain a dictionary

Warum: The XML root does not map to a dictionary structure.

Lösung: Ensure the XML root maps to key/value structure expected by the loader.

`I109` — Source Unsupported File Type¶

Data source '{name}' is not supported by DataSourceRegistry

Warum: The source configuration specifies an unsupported configuration.

Lösung: Use a supported file or adjust the configuration.

`I110` — Source JSON Array Not Acceptable¶

JSON array not acceptable for object mode: '{name}'

Warum: Object mode expects a JSON object but an array was provided.

Lösung: Use object mode with an object root or switch to array mode.

`I111` — Source JSON Object Mode Unsupported¶

Unsupported JSON root for object mode in '{name}'

Warum: Object mode is not supported for the provided JSON root type.

Lösung: Use array mode or adjust the JSON root to a supported type.

`I112` — Source JSON Wrappable Required¶

JSON file '{name}' must be an array or an object (wrappable)

Warum: The JSON root is not an array or object and cannot be wrapped.

Lösung: Provide a JSON array or object at the root.

`I113` — Source Template Empty¶

Template source '{name}' is empty

Warum: The template file exists but contains no usable content.

Lösung: Provide non-empty template content before running the task.

`I114` — Source Template Not Found¶

Template file '{name}' not found in task workspace

Warum: The template file referenced by the source could not be located in the task workspace.

Lösung: Upload the template file or correct the template path.

`I115` — Source Template Invalid XML¶

Invalid XML in template '{name}'

Warum: The configuration provides an invalid XML in template '{name}'.

Lösung: Correct the template file to a valid value or configuration.

`I116` — Source Expr Not String¶

Source expression must evaluate to a string

Warum: The configuration violates the requirement that Source expression must evaluate to a string.

Lösung: Set the source to a string value.

`I117` — Source Expr Item Not String¶

Item source expression for must evaluate to a string

Warum: The configuration violates the requirement that Item source expression for must evaluate to a string.

Lösung: Set the source to a string value.

`I118` — Source Expr Nested Not String¶

NestedKey source expression must evaluate to a string

Warum: The configuration violates the requirement that NestedKey source expression must evaluate to a string.

Lösung: Set the source to a string value.

`I119` — Source Expr Eval Failed¶

Failed to evaluate source expression '{expr}': {error}

Warum: The system failed to evaluate source expression '{expr}': {error}.

Lösung: Fix the expression or script and retry.

`I120` — Source Client Unsupported¶

Cannot load data from client: {client_type}

Warum: The system could not load data from client: {client_type}.

Lösung: Use a supported client or adjust the configuration.

`I121` — Source Unknown Client¶

Unknown database client '{client_id}' for '{stmt_name}'. Check your configuration or source_client attribute.

Warum: The configuration references an unknown database client '{client_id}' for '{stmt_name}'. Checkyour configuration or source_client attribute.

Lösung: Correct the client to a valid value or configuration.

`I122` — Source Unknown¶

Unknown source for '{stmt_name}': source='{source}' did not match any configured client id. {known_msg} To use an ML model, use 'ml://' or set type="ml-model" with source="".

Warum: The source identifier did not match any configured client or supported source type.

Lösung: Use a configured client id or ML source syntax (ml://) and retry.

`I123` — Source Object Storage Bucket Missing¶

Object storage requires a non-empty 'bucket' (MinIO/S3) or 'container' (Azure)

Warum: A required object storage is missing in the source configuration.

Lösung: Provide the required object storage configuration and retry.

`I124` — Source Object Storage Bucket Attr Missing¶

Object-storage source of '{stmt_name}' requires attribute 'bucket' (for AWS, Minio) or 'container' (for Azure)

Warum: A required object storage is missing in the source configuration.

Lösung: Provide the required object storage configuration and retry.

`I125` — Source Object Storage URI Missing¶

Object-storage source of '{stmt_name}' requires attribute 'source_uri'

Warum: A required object storage is missing in the source configuration.

Lösung: Provide the required object storage configuration and retry.

`I126` — Source Object Storage Object Not Found¶

Object '{object_name}' not found in bucket '{bucket}'

Warum: The referenced object storage could not be found for the source configuration.

Lösung: Ensure the referenced object storage configuration exists and the identifier/path is correct.

`I127` — Source Object Storage Invalid Payload¶

Invalid {kind} in object '{object_name}' in bucket '{bucket}'

Warum: The configuration provides an invalid {kind} in object '{object_name}' in bucket '{bucket}'.

Lösung: Correct the object storage configuration to a valid value or configuration.

`I128` — Source Object Storage Unsupported Type¶

Unsupported object type for '{object_name}' in bucket '{bucket}'. Supported extensions: .csv, .json, .parquet, .xml

Warum: The configuration uses an unsupported object type for '{object_name}' in bucket '{bucket}'.Supported extensions: .csv, .json, .parquet, .xml.

Lösung: Use a supported object storage configuration or adjust the configuration.

`I129` — Source DB Query Client Missing¶

Database query requested but client was None

Warum: A required database query is missing in the source configuration.

Lösung: Provide the required database query and retry.

`I130` — Source DB Table Client Missing¶

Database table requested but client was None

Warum: A required database table is missing in the source configuration.

Lösung: Provide the required database table and retry.

`I131` — Source Memstore Task ID Missing¶

task_id is required for Redis memstore

Warum: A required configuration is missing in the source configuration.

Lösung: Provide the required source and retry.

`I132` — Source Unsupported Type¶

Unsupported source type: {source_type}

Warum: The configuration uses an unsupported source type: {source_type}.

Lösung: Use a supported source or adjust the configuration.

`I133` — Source Item Unsupported¶

Cannot load data from source '{source}' of in '{list_name}'

Warum: The system could not load data from source '{source}' of in '{list_name}'.

Lösung: Use a supported source or adjust the configuration.

`I134` — Source File Path Not String¶

File source requires a string path (got {value_type})

Warum: A value expected to be a string was not a string in the source configuration.

Lösung: Set the file to a string value.

`I135` — Source Index Required¶

Order key '{key_col}' for table '{table}' is not indexed while ds_require_index is enabled

Warum: The configured order key is not indexed while ds_require_index is enabled.

Lösung: Add an index for the order key or disable ds_require_index in platform_json.

`I136` — Source ML Unknown¶

Unknown source for '{stmt_name}': source='{source}'. {details}

Warum: The configuration references an unknown source for '{stmt_name}': source='{source}'. {details}.

Lösung: Correct the source to a valid value or configuration.

`I137` — Source Project Ctx Missing¶

Project file sources require a descriptor_dir context

Warum: Project file sources require a descriptor_dir context, but none was available.

Lösung: Run the task with a valid descriptor_dir or avoid project-file sources.

`I138` — Source Project Path Outside Descriptor¶

Project file '{source}' is outside descriptor directory '{descriptor_dir}'

Warum: The project file path resolves outside the descriptor directory.

Lösung: Move the file under descriptor_dir or use object storage instead.

`I139` — Source Project Descriptor Dir Symlink¶

descriptor_dir '{descriptor_dir}' is a symlink (not allowed for project files)

Warum: The descriptor_dir is a symlink, which is not allowed for project file access.

Lösung: Use a real directory path for descriptor_dir.

`I140` — Source Project Symlink Escape¶

Project file '{source}' resolves outside descriptor directory '{descriptor_dir}'

Warum: The project file path resolves outside descriptor_dir due to a symlink.

Lösung: Move the file under descriptor_dir or remove the symlink.

`I141` — Source Project Path Non Local¶

Project file source '{source}' must be a local filesystem path

Warum: The project file path is not a local filesystem path.

Lösung: Use a local path under descriptor_dir or switch to object storage.

`I142` — Source DB Table Not Found¶

Database table '{table}' not found{code_hint}

Warum: The referenced database table could not be found for the source configuration.

Lösung: Ensure the referenced database table exists and the identifier/path is correct.

`I143` — Source DB Column Not Found¶

Database column '{column}' not found{code_hint}

Warum: The referenced database column could not be found for the source configuration.

Lösung: Ensure the referenced database column exists and the identifier/path is correct.

`I144` — Source DB Query Syntax¶

Database query syntax error: {reason}{code_hint}

Warum: The database query syntax is invalid for the source configuration.

Lösung: Review the configuration and retry.

`I145` — Source DB Permission Denied¶

Database permission denied: {reason}{code_hint}

Warum: Access to the database was denied for the source configuration.

Lösung: Grant the required permissions and retry.

`I146` — Source DB Type Mismatch¶

Database query type mismatch: {reason}{code_hint}

Warum: The database type does not match the expected schema for the source configuration.

Lösung: Review the configuration and retry.

`I147` — Source DB Column Ambiguous¶

Database column reference is ambiguous: '{column}'{code_hint}

Warum: An error occurred during source configuration.

Lösung: Review the configuration and retry.

`I148` — Source DB Schema Not Found¶

Database schema '{schema}' not found{code_hint}

Warum: The referenced database schema could not be found for the source configuration.

Lösung: Ensure the referenced database schema exists and the identifier/path is correct.

`I149` — Source DB Function Not Found¶

Database function '{function}' not found{code_hint}

Warum: The referenced database function could not be found for the source configuration.

Lösung: Ensure the referenced database function exists and the identifier/path is correct.

`I150` — Source Mongo Selector Invalid¶

Invalid Mongo selector: {error}

Warum: The configuration provides an invalid Mongo selector: {error}.

Lösung: Correct the Mongo selector to a valid value or configuration.

`I151` — Source Mongo Selector Unsupported¶

Unsupported Mongo selector '{selector}'.Use find:/aggregate: syntax.

Warum: The configuration uses an unsupported Mongo selector '{selector}'.Use find:/aggregate: syntax.

Lösung: Use a supported Mongo selector or adjust the configuration.

`I152` — Source Mongo Permission Denied¶

Mongo permission denied: {reason}

Warum: Access to the Mongo was denied for the source configuration.

Lösung: Grant the required permissions and retry.

`I153` — Source Mongo Namespace Not Found¶

Mongo namespace '{namespace}' not found

Warum: The referenced Mongo could not be found for the source configuration.

Lösung: Ensure the referenced Mongo namespace exists and the identifier/path is correct.

`I154` — Source Mongo Query Invalid¶

Mongo query error: {reason}

Warum: The Mongo value is invalid for the source configuration.

Lösung: Correct the Mongo query to a valid value or configuration.

`I155` — Source DB Connection Failed¶

Database connection failed: {reason}{code_hint}

Warum: The connection failed while accessing the database for the source configuration.

Lösung: Review the configuration and retry.

`I156` — Source DB Timeout¶

Database query timed out: {reason}{code_hint}

Warum: The source configuration timed out while accessing the database.

Lösung: Retry the operation or increase the timeout if appropriate.

`I157` — Source DB Deadlock¶

Database deadlock detected: {reason}{code_hint}

Warum: A database deadlock was detected during the source configuration.

Lösung: Retry the operation or reduce concurrency.

`I158` — Source Object Storage Client Missing¶

Object storage requested but client was None

Warum: Object-storage source loading requires a configured object-storage client instance.

Lösung: Provide a valid object-storage client (or storage id) and retry.

`I159` — Source Kafka Client Missing¶

Kafka source requested but client was None

Warum: Kafka source loading requires a configured Kafka client instance.

Lösung: Provide a valid Kafka client and retry.

`I160` — Source Return Type Unsupported¶

Return type '{return_type}' is not supported for source type '{source_type}'

Warum: The requested return type is incompatible with the selected source type.

Lösung: Use a compatible return type for the source type and retry.

`I161` — Source Massive Mode Fallback Blocked¶

Massive mode blocked fallback '{fallback}' for backend '{backend}' in '{operation}'

Warum: The selected source path would use an unsafe fallback for large-scale reads.

Lösung: Use keyset/range-based paging paths or disable massive mode for compatibility reads.

`I162` — Source DB Route Unsupported Client¶

Unsupported database client type for source routing: {client_type}

Warum: Database source routing could not classify the configured client implementation.

Lösung: Use a supported database client adapter for RDBMS or MongoDB sources.

`I163` — Source DB Query Or Table Required¶

Database source requires either 'query' or 'table_name'

Warum: Database source loading was requested without a query or table name.

Lösung: Set a valid query or table_name in the source configuration and retry.

`I164` — Source Kafka Client Unsupported API¶

Kafka client '{client_type}' must implement consume_iter_message(count)

Warum: The configured Kafka client does not implement the required consume API contract.

Lösung: Use a Kafka client adapter that implements consume_iter_message.

`I165` — Source Return Payload Type Mismatch¶

Return type '{return_type}' for source type '{source_type}' expected payload type '{expected_type}', got '{actual_type}'

Warum: The source loader returned a payload that violates the return-type contract.

Lösung: Use a compatible source/return_type combination or fix the source loader contract.

`I166` — Source Load Kwarg Unsupported¶

Unsupported load parameter(s) '{params}' for source type '{source_type}'. Allowed parameters: {allowed_params}

Warum: DataSourceRegistry.load received unsupported parameters for the selected source type.

Lösung: Remove unsupported parameters or switch to a source type that supports them.

`I167` — Source Kafka TLS Failed¶

Kafka TLS/SSL handshake failed for topic '{topic}': {reason}

Warum: The Kafka source client failed the TLS/SSL handshake while reading messages.

Lösung: Verify Kafka TLS certificate paths, trust chain, hostname validation, and protocol settings.

`I168` — Source Kafka Authentication Failed¶

Kafka authentication failed for topic '{topic}': {reason}

Warum: The Kafka source client could not authenticate with the configured credentials.

Lösung: Verify SASL/TLS identity settings and credentials for the Kafka source client.

`I169` — Source Kafka Authorization Failed¶

Kafka authorization failed for topic '{topic}': {reason}

Warum: The Kafka source client was authenticated but lacks permissions for the topic/resource.

Lösung: Grant required read permissions for the topic and related Kafka resources.

`I170` — Source Kafka Network Failed¶

Kafka network connectivity failed for topic '{topic}': {reason}

Warum: The Kafka source client could not reach the configured broker endpoint.

Lösung: Verify bootstrap server host/port, DNS, routing, and firewall connectivity.

`I171` — Source Kafka Timeout¶

Kafka read timed out for topic '{topic}': {reason}

Warum: The Kafka source operation exceeded the configured timeout while reading messages.

Lösung: Retry or tune Kafka consumer timeout settings for this workload.

`I172` — Source Kafka Topic Not Found¶

Kafka topic/resource not found for topic '{topic}': {reason}

Warum: The configured Kafka topic/resource was not found or is not accessible.

Lösung: Verify the topic exists, is spelled correctly, and is visible to the client.

`I173` — Source Kafka Read Failed¶

Kafka source read failed for topic '{topic}': {reason}

Warum: The Kafka source client failed while reading messages due to an unexpected runtime error.

Lösung: Review Kafka client configuration and runtime logs, then retry the operation.

`I174` — Source Manifest Ambiguous¶

Ambiguous range manifest match for table '{table}'. Matching manifests: {candidates}

Warum: Multiple range manifests match the same table identifier, so shard routing is not deterministic.

Lösung: Use fully-qualified table names per source or clear stale manifests before retrying.

`I175` — Source Manifest Bounds Worker Mismatch¶

Manifest '{manifest_id}' for table '{table}' has {bounds_count} bounds but run expects {workers} workers

Warum: The precomputed manifest bounds do not align with active worker count, so range assignment is invalid.

Lösung: Recompute manifests for the current worker count and retry the run.

`I176` — Source Manifest Init Timeout¶

Manifest '{manifest_id}' lease initialization timed out after {wait_seconds}s for owner '{owner}' (observed_state={observed_state}, init_owner={init_owner}, init_ts={init_ts}, failure_reason={failure_reason}, ready={ready}, leased={leased}, done={done}, total={total})

Warum: The lease scheduler did not expose a usable shard queue before the init wait budget elapsed.

Lösung: Treat this as run-fatal and retry after verifying Redis lease keys and worker startup ordering.

`I177` — Source Manifest State Inconsistent¶

Manifest '{manifest_id}' is inconsistent for owner '{owner}': (ready={ready}, leased={leased}, done={done}, total={total}, init_ts={init_ts})

Warum: Lease state shows unfinished work but no valid leasing state could be derived deterministically.

Lösung: Treat this as run-fatal; verify scheduler state and retry with a fresh task namespace.

`I178` — Source Manifest Stale Lease¶

Manifest '{manifest_id}' lease for owner '{owner}' and shard '{shard_id}' is no longer valid and cannot be resumed safely

Warum: The worker attempted to resume a stored shard lease that could not be renewed deterministically.

Lösung: Treat this as run-fatal; retry the run with a fresh task namespace or new task id because stale local continuation is not safe to resume.

`I179` — Source Continuation State Failed¶

Continuation state operation '{operation}' failed for scope '{scope}': {error}

Warum: The run-scoped continuation state in Redis could not be persisted or loaded deterministically.

Lösung: Treat this as run-fatal; verify Redis availability and retry the run with a fresh task namespace.

`I180` — Source Lease Infrastructure Failed¶

Lease operation '{operation}' failed for manifest '{manifest_id}', owner '{owner}', shard '{shard_id}': {error}

Warum: The lease scheduler could not complete a Redis-backed lease operation due to an infrastructure failure.

Lösung: Treat this as run-fatal; verify Redis connectivity and scheduler health, then retry with a fresh task namespace.

`I181` — Source Sharding Plan Unavailable¶

Safe sharding plan unavailable for source '{source}': {reason}

Warum: The runtime could not derive a deterministic shard/coverage plan for a shard-capable multi-worker source.

Lösung: Treat this as run-fatal; verify manifest registration, range planning, and coverage-owner policy before retrying.

`I182` — Source Invalid Parquet¶

Invalid Parquet in '{name}'

Warum: The Parquet file is empty, malformed, or cannot be parsed safely.

Lösung: Replace the Parquet file with a valid single-file Parquet source and retry.

`I183` — Source Object Storage Invalid Parquet¶

Invalid Parquet object '{object_name}' in bucket '{bucket}'

Warum: The object-storage payload is empty, malformed, or cannot be parsed as Parquet.

Lösung: Upload a valid single-file Parquet object and retry.

`I184` — Source Parquet Unsupported Arrow Type¶

Parquet source '{name}' contains unsupported Arrow type '{arrow_type}' in column '{column}'

Warum: The Parquet schema includes an Arrow type that DATAMIMIC v1 does not support.

Lösung: Convert the column to a supported Parquet/Arrow type and retry.

`I185` — Source Parquet Dependency Missing¶

Parquet source support requires dependency 'pyarrow>=14.0.0,<19.0.0'

Warum: The worker environment is missing the required Parquet runtime dependency.

Lösung: Install a supported pyarrow version and rerun the task.

`I186` — Source Parquet Attribute Unsupported¶

Attributes '{attrs}' are not supported for Parquet source '{name}'

Warum: The source configuration uses text/CSV-specific attributes that Parquet does not honor.

Lösung: Remove the unsupported attributes and retry.

`I187` — Source Parquet Batch Too Large¶

Parquet batch in '{name}' exceeds in-memory batch limit after adaptive retry ({limit_mb} MB)

Warum: Even the smallest supported Parquet batch still exceeds the in-memory safety limit.

Lösung: Reduce row width or split the source file into smaller single-file Parquet inputs.

`I188` — Source Parquet Metadata Too Large¶

Parquet metadata in '{name}' exceeds allowed limit ({limit_mb} MB)

Warum: The Parquet footer metadata exceeds the configured safety limit and may be unsafe to read.

Lösung: Regenerate the Parquet file with smaller footer metadata and retry.

`I189` — Source Object Storage Streaming Required For Parquet¶

Parquet object '{object_name}' in bucket '{bucket}' requires a streaming-capable client, but '{client_type}' falls back to eager in-memory reads

Warum: The configured object-storage adapter cannot stream the Parquet object safely and would load it into RAM.

Lösung: Use a streaming-capable object-storage client implementation or switch to a supported adapter.

`I190` — Source Object Storage Parquet Spool Too Large¶

Parquet object '{object_name}' in bucket '{bucket}' exceeds the local spool limit ({size_mb} MB > {limit_mb} MB)

Warum: The object-storage Parquet source is too large to stage safely into the worker-local spool area.

Lösung: Reduce the object size, split the source, or raise the Parquet spool limit if the worker disk budget allows it.

`I191` — Source Object Storage Parquet Size Unknown¶

Parquet object '{object_name}' in bucket '{bucket}' does not expose a size, and runtime policy forbids unbounded spooling

Warum: The object-storage adapter cannot report object size, so the Parquet spool safety limit cannot be enforced.

Lösung: Use an adapter that reports object size or allow unknown-size Parquet spooling in the runtime configuration.

`I192` — Source Reference Identifier Empty¶

Explicit source URI for family '{family}' requires a non-empty identifier

Warum: A recognized source-family URI was declared without the identifier needed to resolve its source.

Lösung: Add the source identifier after the URI scheme and retry.

`I193` — Source Reference Consumer Unsupported¶

Explicit source family '{family}' is not supported by <{consumer}>

Warum: The source family is valid, but the consuming DSL element does not implement its read contract.

Lösung: Use a source family supported by this element or move the read to generate/iterate.

`I194` — Source Reference Client Family Mismatch¶

Explicit source family '{family}' does not match configured client '{client_id}' of type '{actual_client_type}'

Warum: The referenced client exists but does not implement the source family declared by the URI.

Lösung: Use the URI scheme matching the configured client or reference a client of the declared family.

`I195` — Source Reference Identifier Conflict¶

Explicit source identifier '{identifier}' conflicts with {attribute}='{configured_identifier}'

Warum: Two source attributes select different identities for the same explicit source reference.

Lösung: Remove the legacy override or make it equal to the identifier in source.

`I201` — Include File Not Found¶

Include file '{uri}' not found in task workspace

Warum: The referenced configuration could not be found for the include configuration.

Lösung: Ensure the referenced file exists and the identifier/path is correct.

`I202` — Include Properties Parse Failed¶

Failed to parse include properties file '{uri}': {error}

Warum: The system failed to parse include properties file '{uri}': {error}.

Lösung: Fix the input format and retry.

`I203` — Include Unsupported File Type¶

Unsupported include file type '{uri}'. Only .properties and .xml are supported

Warum: The configuration uses an unsupported include file type '{uri}'. Only .properties and .xml are supported.

Lösung: Use a supported file or adjust the configuration.

`I204` — Include Unsupported File Type Generate¶

Unsupported include file type '{uri}' inside . Only .xml is supported

Warum: The configuration uses an unsupported include file type '{uri}' inside . Only .xml is supported.

Lösung: Use a supported file or adjust the configuration.

`I205` — Include Condition Not Boolean¶

Condition '{condition}' for include '{uri}' evaluated to a non-boolean value (not a valid boolean value): {value}

Warum: A condition evaluated to a non-boolean value in the include configuration.

Lösung: Ensure the expression evaluates to true or false.

`I206` — Include Condition Eval Failed¶

Failed to evaluate condition '{condition}' for include '{uri}': {error}

Warum: The system failed to evaluate condition '{condition}' for include '{uri}': {error}.

Lösung: Fix the expression or script and retry.

`I207` — Include Path Outside Descriptor¶

Include path '{uri}' is outside descriptor directory '{descriptor_dir}' or violates relative-path policy: {reason}

Warum: The include path is outside the descriptor directory or does not follow relative-path requirements.

Lösung: Use a relative include path under descriptor_dir.

`I208` — Include Dynamic Properties With Overlay¶

Include '{uri}' resolved to a .properties file, but children are only supported for XML descriptor includes

Warum: The include resolved to a .properties file even though the descriptor configured XML-only property overlays.

Lösung: Remove the children or resolve the include to an XML descriptor.

`I301` — Export SQL Unsupported Dialect¶

Unsupported SQL dialect '{dialect}'

Warum: The configuration uses an unsupported SQL dialect '{dialect}'.

Lösung: Use a supported configuration or adjust the configuration.

`I302` — Export SQL Unsupported Mode¶

Unsupported SQL output mode '{mode}'. Choose one of {modes}.

Warum: The configuration uses an unsupported SQL output mode '{mode}'. Choose one of {modes}.

Lösung: Use a supported configuration or adjust the configuration.

`I303` — Export SQL Invalid Batch Size¶

Invalid batch_size '{value}'

Warum: The configuration provides an invalid batch_size '{value}'.

Lösung: Correct the configuration to a valid value or configuration.

`I304` — Export SQL Batch Size Nonpositive¶

batch_size must be > 0 (got {size})

Warum: The configuration violates the requirement that batch_size must be > 0 (got {size}).

Lösung: Provide a positive integer value.

`I305` — Export SQL Columns Not List¶

columns must be a list of column names

Warum: The configuration violates the requirement that columns must be a list of column names.

Lösung: Provide a list value for the configuration.

`I306` — Export SQL Columns Empty¶

columns must be non-empty strings

Warum: The configuration violates the requirement that columns must be non-empty strings.

Lösung: Provide a non-empty configuration and retry.

`I307` — Export SQL Column Map Not Dict¶

column_map must be a dict mapping source to target names

Warum: The configuration violates the requirement that column_map must be a dict mapping source to target names.

Lösung: Provide a dictionary value for the configuration.

`I308` — Export SQL Column Map Strings¶

column_map keys and values must be strings

Warum: The configuration violates the requirement that column_map keys and values must be strings.

Lösung: Review the configuration and retry.

`I309` — Export SQL Column Map Nonempty¶

column_map keys and values must be non-empty

Warum: The configuration violates the requirement that column_map keys and values must be non-empty.

Lösung: Provide a non-empty configuration and retry.

`I310` — Export SQL Table Name Empty¶

table_name must be a non-empty string

Warum: The configuration violates the requirement that table_name must be a non-empty string.

Lösung: Provide a non-empty configuration and retry.

`I311` — Export SQL Duplicate Columns¶

Duplicate output columns after mapping: {columns}

Warum: The configuration contains duplicate output columns after mapping: {columns}.

Lösung: Remove duplicates or adjust the configuration to avoid conflicts.

`I312` — Export Target Not Found¶

Target not found: {target}. Available exporters: {exporters}. Available clients: {clients}

Warum: The referenced target could not be found for the exporter configuration.

Lösung: Ensure the referenced target exists and the identifier/path is correct.

`I313` — Export Storage Client Not Found¶

Cannot find storage client with id '{storage_id}'

Warum: The system could not find storage client with id '{storage_id}'.

Lösung: Ensure the referenced client exists and the identifier/path is correct.

`I314` — Export Storage Client Unsupported Api¶

Storage client '{client_label}' does not expose the provider-neutral ensure_bucket/write_stream API. Configure a compatible client or provide a client implementation.

Warum: The exporter configuration specifies an unsupported client.

Lösung: Use a supported client or adjust the configuration.

`I315` — Export Storage Bucket Missing¶

Missing default bucket for storage client '{storage_id}'. Configure 'bucket' (MinIO/AWS) or 'container' (Azure) in the block, or pass an explicit bucket on the exporter.

Warum: A required default bucket for storage client '{storage_id}'. Configure 'bucket' (MinIO/AWS) or'container'(Azure) in the block, or pass an explicit bucket on the exporter.

Lösung: Provide the required bucket/container and retry.

`I316` — Export XML Single Multi Root¶

XMLSingle expects exactly one root element; got {count} keys: {keys}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I317` — Export XML Single Root Type¶

First nested key '{root_key}' must contain a dictionary or list, got {value_type}

Warum: The configuration violates the requirement that First nested key '{root_key}' must contain a dictionaryorlist, got {value_type}.

Lösung: Review the configuration and retry.

`I318` — Export Target Parse Failed¶

Failed to parse exporter target(s) '{targets}': {error}

Warum: The system failed to parse exporter target(s) '{targets}': {error}.

Lösung: Fix the input format and retry.

`I319` — Export Param Non Literal¶

Exporter parameter '{param}' must be a literal value; got {value}

Warum: The configuration violates the requirement that Exporter parameter '{param}' must be a literal value;got{value}.

Lösung: Review the configuration and retry.

`I320` — Export Operation Unsupported¶

Unsupported operation '{operation}' for client '{client_name}'. Allowed operations: {allowed}

Warum: The configuration uses an unsupported operation '{operation}' for client '{client_name}'. Allowedoperations:{allowed}.

Lösung: Use a supported configuration or adjust the configuration.

`I321` — Export Operation Unsupported Client¶

Unsupported client type '{client_type}' for operation '{operation}'

Warum: The configuration uses an unsupported client type '{client_type}' for operation '{operation}'.

Lösung: Use a supported client or adjust the configuration.

`I322` — Export Dynamic Target Entity Unsupported¶

Dynamic targetEntity is only supported for routing-capable exporters (TemplateSingle, JSONSingle, XMLSingle, mem). Unsupported targets: {targets}

Warum: Dynamic targetEntity was set for exporters that do not support it.

Lösung: Use TemplateSingle/JSONSingle/XMLSingle/mem or remove dynamic targetEntity values.

`I323` — Export Storage Connect Failed¶

Failed to connect to storage client '{storage_id}': {reason}

Warum: The system failed to connect to storage client '{storage_id}': {reason}.

Lösung: Review the configuration and retry.

`I324` — Export URI Requires Custom Storage¶

exportUri is only supported with a custom object storage client; got storageId='{storage_id}'

Warum: exportUri was provided without a custom object storage client.

Lösung: Set storageId to a custom id or remove exportUri.

`I325` — Export URI Invalid¶

Invalid exportUri '{export_uri}': {reason}

Warum: exportUri does not match the required path format.

Lösung: Provide a relative path prefix using letters, numbers, '/', '-', '_', '.', or '='.

`I326` — Export Dynamic Target Entity Mixed¶

Mixed dynamic targetEntity usage for exporter '{exporter_name}': some records include target_entity and others do not

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I327` — Export Template Path Mixed¶

TemplateSingle expects a single template path; got '{current_path}' after '{expected_path}'

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I328` — Export DB Table Not Found¶

Target table '{table}' not found in the database{dependency_clause}{code_hint}

Warum: The referenced database table could not be found for the exporter configuration.

Lösung: Ensure the referenced database table exists and the identifier/path is correct.

`I329` — Export Mongo Duplicate Key¶

Duplicate key error while writing to Mongo collection '{collection}': {reason}

Warum: The configuration contains duplicate key error while writing to Mongo collection '{collection}': {reason}.

Lösung: Ensure values are unique or adjust constraints, then retry.

`I330` — Export Mongo Write Not Allowed¶

Mongo write not allowed for collection '{collection}': {reason}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I331` — Export Mongo Validation Failed¶

Mongo validation failed for collection '{collection}': {reason}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I332` — Export Mongo Namespace Not Found¶

Mongo namespace '{namespace}' not found

Warum: The referenced Mongo could not be found for the exporter configuration.

Lösung: Ensure the referenced Mongo namespace exists and the identifier/path is correct.

`I333` — Export DB Column Not Found¶

Target column '{column}' not found on table '{table}'{code_hint}

Warum: The referenced database column could not be found for the exporter configuration.

Lösung: Ensure the referenced database column exists and the identifier/path is correct.

`I334` — Export DB Schema Not Found¶

Database schema '{schema}' not found{code_hint}

Warum: The referenced database schema could not be found for the exporter configuration.

Lösung: Ensure the referenced database schema exists and the identifier/path is correct.

`I335` — Export DB Permission Denied¶

Database permission denied for table '{table}': {reason}{code_hint}

Warum: Access to the database was denied for the exporter configuration.

Lösung: Grant the required permissions and retry.

`I336` — Export DB Type Mismatch¶

Database type mismatch while writing to '{table}': {reason}{code_hint}

Warum: The database type does not match the expected schema for the exporter configuration.

Lösung: Review the configuration and retry.

`I337` — Export DB Duplicate Key¶

Duplicate key error while writing to '{table}': {reason}{code_hint}

Warum: The configuration contains duplicate key error while writing to '{table}': {reason}.

Lösung: Ensure values are unique or adjust constraints, then retry.

`I338` — Export DB Not Null Violation¶

Null value violates NOT NULL constraint on '{table}': {reason}{code_hint}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I339` — Export DB Foreign Key Violation¶

Foreign key constraint violation on '{table}': {reason}{code_hint}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I340` — Export DB Check Violation¶

Check constraint violation on '{table}': {reason}{code_hint}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I341` — Export DB Connection Failed¶

Database connection failed while writing to '{table}': {reason}{code_hint}

Warum: The connection failed while accessing the database for the exporter configuration.

Lösung: Review the configuration and retry.

`I342` — Export DB Timeout¶

Database write timed out for '{table}': {reason}{code_hint}

Warum: The exporter configuration timed out while accessing the database.

Lösung: Retry the operation or increase the timeout if appropriate.

`I343` — Export DB Deadlock¶

Database deadlock detected while writing to '{table}': {reason}{code_hint}

Warum: A database deadlock was detected during the exporter configuration.

Lösung: Retry the operation or reduce concurrency.

`I344` — Export Storage Access Denied¶

Storage access denied for bucket '{bucket}': {reason}

Warum: Access to the configuration was denied for the exporter configuration.

Lösung: Grant the required permissions and retry.

`I345` — Export Storage Bucket Not Found¶

Storage bucket '{bucket}' not found

Warum: The referenced configuration could not be found for the exporter configuration.

Lösung: Ensure the referenced bucket/container exists and the identifier/path is correct.

`I346` — Export Storage Write Failed¶

Storage write failed for bucket '{bucket}' object '{object_name}': {reason}

Warum: An error occurred during exporter configuration.

Lösung: Review the configuration and retry.

`I347` — Export Storage Connect Access Denied¶

Storage access denied for client '{storage_id}': {reason}

Warum: Access to the configuration was denied for the exporter configuration.

Lösung: Grant the required permissions and retry.

`I348` — Export Flush Failed¶

Exporter flush failed: {detail}

Warum: An exporter failed while flushing buffered records.

Lösung: Inspect the reported exporter details and resolve the underlying target write error.

`I349` — Export Kafka TLS Failed¶

Kafka TLS/SSL handshake failed for topic '{topic}': {reason}

Warum: Kafka producer failed during TLS/SSL negotiation while exporting records.

Lösung: Verify Kafka TLS certificate paths, key material, and security protocol settings.

`I350` — Export Kafka Authentication Failed¶

Kafka authentication failed for topic '{topic}': {reason}

Warum: Kafka producer credentials were rejected while exporting records.

Lösung: Verify SASL credentials/mechanism and retry with valid authentication settings.

`I351` — Export Kafka Authorization Failed¶

Kafka authorization failed for topic '{topic}': {reason}

Warum: Kafka producer lacks permissions for the configured topic.

Lösung: Grant write permissions for the topic or update ACLs and retry.

`I352` — Export Kafka Network Failed¶

Kafka network connectivity failed for topic '{topic}': {reason}

Warum: Kafka producer could not establish broker connectivity while exporting records.

Lösung: Verify broker hosts/ports, DNS, routing, and firewall configuration.

`I353` — Export Kafka Timeout¶

Kafka operation timed out for topic '{topic}': {reason}

Warum: Kafka producer operation exceeded configured timeout while exporting records.

Lösung: Retry the operation or tune Kafka timeout settings for the environment.

`I354` — Export Kafka Topic Not Found¶

Kafka topic '{topic}' not found or inaccessible: {reason}

Warum: Configured Kafka topic does not exist or cannot be accessed by the producer.

Lösung: Ensure the topic exists and the producer has access to it.

`I355` — Export Kafka Write Failed¶

Kafka write failed for topic '{topic}': {reason}

Warum: Kafka producer encountered an unclassified write failure while exporting records.

Lösung: Inspect broker/client logs and producer configuration, then retry.

`I356` — Export Memstore Product Invalid¶

Invalid memstore product name '{product_name}' resolved for exporter '{exporter_name}'. Expected pattern: {pattern}

Warum: The effective memstore product name resolved from targetEntity is empty or contains unsupported characters.

Lösung: Adjust targetEntity so it resolves to a valid memstore product name and retry.

`I357` — Export XLSX Cell Limit Exceeded¶

XLSX cell in column '{column}' holds {length} characters, exceeding Excel's hard limit of {limit} characters per cell; the value would be silently truncated

Warum: A generated value (for example a large binary payload encoded as base64) is longer than the 32,767-character Excel cell limit.

Lösung: Reduce the value size (e.g. a smaller binary maxLength) or export the field to a format without cell limits such as CSV, JSON, or Parquet.

`I358` — Export Static Single File Artifact Collision¶

Static single-file artifact '{artifact}' is configured by both generate statements '{first_statement}' and '{second_statement}'

Warum: Both generate statements resolve to the same object-storage output series. Object storage overwrites existing object keys.

Lösung: Give one target a distinct exported_name, exported_prefix, exported_suffix, storageId, or exportUri and retry.

`I401` — Generator Init Failed¶

Failed to initialise generator '{generator_decl}' for <{element_tag}> '{stmt_path}'. Cannot create generator '{class_name}' for element '{element_name}'{descriptor}{context_msg}: {error}

Warum: The system failed to initialise generator '{generator_decl}' for <{element_tag}> '{stmt_path}'. Cannotcreategenerator '{class_name}' for element '{element_name}'{descriptor}{context_msg}: {error}.

Lösung: Review the configuration and retry.

`I402` — Generator Faker Method Unsupported¶

Faker method '{method}' is not supported

Warum: The generator configuration specifies an unsupported generator.

Lösung: Use a supported generator or adjust the configuration.

`I403` — Generator Faker Method Missing¶

Faker method '{method}' does not exist

Warum: A required generator is missing in the generator configuration.

Lösung: Provide the required generator and retry.

`I404` — Generator Invalid Gender¶

Invalid gender: {gender}

Warum: The configuration provides an invalid gender: {gender}.

Lösung: Correct the generator to a valid value or configuration.

`I405` — Datetime Eval Expression Failed¶

Failed to evaluate {name} expression: {value}. Weights accept a literal number list, [x]*N repetition and + concatenation; comprehensions and other Python are not supported.

Warum: The {name} expression is not a literal list, repetition, or concatenation: {value}.

Lösung: Rewrite it as a literal list, for example [1]+[0]14+[1]+[0]14+[1]+[0]14+[1]+[0]14.

`I406` — Datetime Invalid Range¶

Invalid range '{range}' in spec '{spec}'

Warum: The configuration provides an invalid range '{range}' in spec '{spec}'.

Lösung: Correct the configuration to a valid value or configuration.

`I407` — Datetime Value Out Of Bounds¶

Value {value} out of bounds [{low},{high}] in spec '{spec}'

Warum: A value is outside the allowed bounds for the generator configuration.

Lösung: Provide values within the allowed bounds or range.

`I408` — Datetime Invalid Value¶

Invalid value '{value}' in spec '{spec}'

Warum: The configuration provides an invalid value '{value}' in spec '{spec}'.

Lösung: Correct the configuration to a valid value or configuration.

`I409` — Datetime Months Entries Range¶

months entries must be 1..12

Warum: The configuration violates the requirement that months entries must be 1..12.

Lösung: Provide values within the allowed bounds or range.

`I410` — Datetime Months Invalid¶

months must be a string like '1,3-5,Q1' or a list of integers in 1..12

Warum: The configuration violates the requirement that months must be a string like '1,3-5,Q1' or a list ofintegersin 1..12.

Lösung: Correct the configuration to a valid value or configuration.

`I411` — Datetime Weekday Range Invalid¶

Invalid weekday range '{token}'

Warum: The configuration provides an invalid weekday range '{token}'.

Lösung: Correct the configuration to a valid value or configuration.

`I412` — Datetime Weekday Token Invalid¶

Invalid weekday token '{token}'

Warum: The configuration provides an invalid weekday token '{token}'.

Lösung: Correct the configuration to a valid value or configuration.

`I413` — Datetime Weekday Index Bounds¶

Weekday index {value} out of bounds [0,6]

Warum: An error occurred during generator configuration.

Lösung: Review the configuration and retry.

`I414` — Datetime Weekday List Range¶

weekday list values must be 0..6

Warum: The configuration violates the requirement that weekday list values must be 0..6.

Lösung: Provide values within the allowed bounds or range.

`I415` — Datetime Weekday List Invalid¶

weekday list values must be ints or weekday names

Warum: The configuration violates the requirement that weekday list values must be ints or weekday names.

Lösung: Correct the configuration to a valid value or configuration.

`I416` — Datetime Weekdays Invalid¶

weekdays must be a string like 'Mon-Fri,weekend' or a list of ints (0..6) or names

Warum: The configuration violates the requirement that weekdays must be a string like 'Mon-Fri,weekend' or a listofints (0..6) or names.

Lösung: Correct the configuration to a valid value or configuration.

`I417` — Datetime Dom Value Range¶

dom values must be 1..31 or 'last'

Warum: The configuration violates the requirement that dom values must be 1..31 or 'last'.

Lösung: Provide values within the allowed bounds or range.

`I418` — Datetime Dom List Invalid¶

dom list values must be ints or 'last'

Warum: The configuration violates the requirement that dom list values must be ints or 'last'.

Lösung: Correct the configuration to a valid value or configuration.

`I419` — Datetime Dom Range Invalid¶

Invalid dom range '{token}'

Warum: The configuration provides an invalid dom range '{token}'.

Lösung: Correct the configuration to a valid value or configuration.

`I420` — Datetime Dom Token Invalid¶

Invalid dom token '{token}'

Warum: The configuration provides an invalid dom token '{token}'.

Lösung: Correct the configuration to a valid value or configuration.

`I421` — Datetime Dom Invalid¶

dom must be a string like '1-5,15,last' or a list of ints and/or 'last'

Warum: The configuration violates the requirement that dom must be a string like '1-5,15,last' or a list ofintsand/or 'last'.

Lösung: Correct the configuration to a valid value or configuration.

`I422` — Datetime Hours Preset Unknown¶

Unknown hours_preset '{preset}' (supported: office, night, flat)

Warum: The configuration references an unknown hours_preset '{preset}' (supported: office, night, flat).

Lösung: Correct the configuration to a valid value or configuration.

`I423` — Datetime Granularity Range¶

granularity must be in 1..{limit}

Warum: The configuration violates the requirement that granularity must be in 1..{limit}.

Lösung: Provide values within the allowed bounds or range.

`I424` — Datetime Weights Length¶

{name} must have length {expected_len}

Warum: The configuration violates the requirement that {name} must have length {expected_len}.

Lösung: Review the configuration and retry.

`I425` — Datetime Weights Negative¶

{name} must be non-negative

Warum: The configuration violates the requirement that {name} must be non-negative.

Lösung: Review the configuration and retry.

`I426` — Datetime Weights Sum Zero¶

{name} must not sum to zero

Warum: The configuration violates the requirement that {name} must not sum to zero.

Lösung: Review the configuration and retry.

`I427` — Datetime Value Format Mismatch¶

value '{value}' does not match input_format '{input_format}'

Warum: An error occurred during generator configuration.

Lösung: Review the configuration and retry.

`I428` — Datetime Min Format Mismatch¶

min '{value}' does not match input_format '{input_format}'

Warum: An error occurred during generator configuration.

Lösung: Review the configuration and retry.

`I429` — Datetime Max Format Mismatch¶

max '{value}' does not match input_format '{input_format}'

Warum: An error occurred during generator configuration.

Lösung: Review the configuration and retry.

`I430` — Datetime Max Before Min¶

max_datetime must be greater than min_datetime

Warum: The configuration violates the requirement that max_datetime must be greater than min_datetime.

Lösung: Review the configuration and retry.

`I431` — Datetime Epoch Unit Invalid¶

epoch_unit must be 'seconds' or 'milliseconds'

Warum: The configuration violates the requirement that epoch_unit must be 'seconds' or 'milliseconds'.

Lösung: Correct the configuration to a valid value or configuration.

`I432` — Datetime Non Datetime To Epoch¶

Cannot convert non-datetime to epoch: {value}

Warum: The system could not convert non-datetime to epoch: {value}.

Lösung: Review the configuration and retry.

`I433` — Datetime Value Not Datetime¶

Generated datetime value is not a datetime: {value}

Warum: An error occurred during generator configuration.

Lösung: Review the configuration and retry.

`I434` — Datetime No Eligible Dates¶

No eligible dates within the range after applying month/weekday/dom weights.

Warum: An error occurred during generator configuration.

Lösung: Review the configuration and retry.

`I435` — Generator Unknown¶

Unknown generator '{class_name}' for element '{element_name}'{descriptor}

Warum: The configuration references an unknown generator '{class_name}' for element '{element_name}'{descriptor}.

Lösung: Correct the generator to a valid value or configuration.

`I436` — Generator Create Failed¶

Cannot create generator '{class_name}' for element '{element_name}'{descriptor}: {error}

Warum: The system could not create generator '{class_name}' for element '{element_name}'{descriptor}: {error}.

Lösung: Review the configuration and retry.

`I437` — Datetime Reference Invalid¶

Invalid datetime reference '{reference}'. Supported forms: {allowed}

Warum: The datetime generator reference '{reference}' does not match the supported lookup-only contract.

Lösung: Use a bare identifier, this., this.parent., or root..

`I501` — Condition Duplicate If¶

Fail while parsing . Only one tag is allowed in .

Warum: A block contains more than one first branch, so branch order is ambiguous.

Lösung: Keep exactly one as the first child; add further conditions as children.

`I502` — Condition If Missing¶

Fail while parsing . Must have as the first tag.

Warum: A block has no initial branch to establish the first decision.

Lösung: Add exactly one as the first child.

`I503` — Condition Else After¶

Fail while parsing . Tag must be the last tag.

Warum: An branch is followed by another branch, but is the unconditional final fallback.

Lösung: Move after every and branch.

`I504` — Condition Else Duplicate¶

Fail while parsing . There can only be one tag at most.

Warum: A block contains more than one unconditional fallback branch.

Lösung: Keep at most one , after all and branches.

`I505` — Condition Invalid Tag¶

Invalid tag {tag} in .

Warum: The branch container accepts only , , and optional final children.

Lösung: Replace <{tag}> with a supported branch element or move it inside an existing branch.

`I506` — Condition Eval Failed¶

Failed to evaluate condition '{condition}' for {element_label}: {error}

Warum: The system failed to evaluate condition '{condition}' for {element_label}: {error}.

Lösung: Fix the expression or script and retry.

`I507` — Condition Not Boolean¶

Condition '{condition}' for {element_label} evaluated to a non-boolean value (not a valid boolean value): {value}

Warum: A condition evaluated to a non-boolean value in the condition configuration.

Lösung: Ensure the expression evaluates to true or false.

`I601` — Parser Reserved Name¶

Element <{element_tag}> name '{name}' is a reserved name (conflicts with registered generator/converter), please use another name

Warum: An error occurred during descriptor parsing.

Lösung: Review the configuration and retry.

`I602` — Parser Invalid Tag¶

Expect element tag name '{expected}', but got '{actual}'

Warum: The configuration value is invalid for the descriptor parsing.

Lösung: Correct the configuration to a valid value or configuration.

`I603` — Parser No Subelements Allowed¶

Element <{element_tag}>{parent_clause} does not accept any sub-elements

Warum: An error occurred during descriptor parsing.

Lösung: Review the configuration and retry.

`I604` — Parser Invalid Child¶

Element <{element_tag}> got invalid child <{child_tag}>, expects: {expected}

Warum: The configuration value is invalid for the descriptor parsing.

Lösung: Correct the configuration to a valid value or configuration.

`I605` — Parser Validation Failed¶

{details}

Warum: An error occurred during descriptor parsing.

Lösung: Review the configuration and retry.

`I606` — Parser Unknown Statement¶

Cannot get element tag for statement {statement}

Warum: The system could not get element tag for statement {statement}.

Lösung: Correct the statement to a valid value or configuration.

`I607` — Parser Unknown Element¶

Unknown element <{element_tag}> in descriptor

Warum: The configuration references an unknown element <{element_tag}> in descriptor.

Lösung: Correct the configuration to a valid value or configuration.

`I608` — Parser Cannot Parse Element¶

Cannot parse element <{element_tag}>

Warum: The system could not parse element <{element_tag}>.

Lösung: Review the configuration and retry.

`I609` — Parser Descriptor Not Found¶

Descriptor file '{name}' not found in task workspace

Warum: The referenced script could not be found for the descriptor parsing.

Lösung: Ensure the referenced script exists and the identifier/path is correct.

`I610` — Parser Descriptor Invalid XML¶

Descriptor XML '{name}' is not well-formed at {location}

Warum: The XML value is invalid for the descriptor parsing.

Lösung: Correct the XML content to a valid value or configuration.

`I611` — Parser Array Subelements Not Allowed¶

Element '{name}' does not accept sub-elements unless type is '{data_type}'

Warum: An error occurred during descriptor parsing.

Lösung: Review the configuration and retry.

`I612` — Parser Array Literal Empty¶

Literal array '{name}' must define at least one element

Warum: The configuration violates the requirement that Literal array '{name}' must define at least oneelement.

Lösung: Provide a non-empty configuration and retry.

`I613` — Parser Array Value Invalid¶

Failed while parsing attributes of element <{child_tag}> inside '{name}': {details}

Warum: The system failed while parsing attributes of element <{child_tag}> inside '{name}': {details}.

Lösung: Correct the configuration to a valid value or configuration.

`I614` — Parser Execute Invalid Source¶

requires exactly one code source: uri (a script file), inline text, or script (an expression).

Warum: has no code source or combines uri, inline text, and script even though they are alternatives.

Lösung: Provide exactly one source: uri= for a file, script= with type=, or an inline element body.

`I616` — Parser Include Property Duplicate¶

Duplicate in is not allowed

Warum: The include configuration defines the same scoped property name more than once.

Lösung: Remove or rename the duplicate entry.

`I617` — Parser Include Property On Properties¶

Element cannot define children for .properties includes

Warum: Scoped include properties are only supported when the include target is an XML descriptor.

Lösung: Remove the children or change the include target to an XML descriptor.

`I618` — Parser Include Param Missing¶

Fragment contract violation for

{contract_table}

{missing_summary}

Warum: The included fragment declares required params that were not supplied by the caller.

Lösung: Supply the missing values or define defaults on the fragment declarations.

`I619` — Parser Include Param Invalid Value¶

Invalid value for param '{param_name}' in . Expected {expected_detail}; provided '{provided_value}'

Warum: The include caller supplied a literal value that does not satisfy the fragment param contract.

Lösung: Update the value to match the declared param type or enum values.

`I620` — Parser Param In Top Level Descriptor¶

declarations have no effect in top-level descriptors

Warum: Fragment param declarations are only consumed when a descriptor is used as an included XML fragment.

Lösung: Move the declarations into a fragment descriptor or remove them from the top-level descriptor.

`I621` — Parser AMA Reference Invalid¶

AMA {reference_kind} '{reference}' is invalid: {reason}

Warum: The AMA block contains a duplicate identifier or an unresolved local reference.

Lösung: Declare each profile and template once, then reference an existing identifier.

`I701` — Client System Type Unsupported¶

System type '{system_type}' is not supported

Warum: The client/runtime configuration specifies an unsupported client.

Lösung: Use a supported client or adjust the configuration.

`I702` — Client Preflight Failed¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: An error occurred during client/runtime configuration.

Lösung: Review the configuration and retry.

`I703` — Client Missing Fields¶

Missing required field(s) {fields} in project environment configuration for .

Warum: The object-storage client configuration is missing required fields.

Lösung: Provide all required fields for the object-storage client.

`I704` — Client Env Properties Parse Failed¶

Failed to parse environment properties file '{path}': {error}

Warum: The system failed to parse environment properties file '{path}': {error}.

Lösung: Fix the input format and retry.

`I705` — Client Object Storage Missing¶

Object storage client required for '{name}'

Warum: A required object storage is missing in the client/runtime configuration.

Lösung: Provide the required object storage configuration and retry.

`I706` — Runtime Config Invalid JSON¶

Invalid platform_json: {error}

Warum: platform_json is not valid JSON or not a JSON object string.

Lösung: Provide platform_json as a JSON object string using double quotes.

`I707` — Client Preflight Missing Field¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: A required connection field is missing in project environment configuration.

Lösung: Provide the missing field in the client configuration and retry.

`I708` — Client Preflight Invalid Configuration¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: The connection configuration failed validation before connectivity checks.

Lösung: Fix the configuration values and retry.

`I709` — Client Preflight Authentication Failed¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: Credentials or identity settings were rejected by the target system.

Lösung: Verify credentials, auth mechanism settings, and retry.

`I710` — Client Preflight TLS Failed¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: TLS/SSL handshake validation failed for the connection.

Lösung: Check certificate files, trust chain, hostnames, and TLS protocol settings.

`I711` — Client Preflight Network Failed¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: The runtime could not establish a network path to the configured endpoint.

Lösung: Verify host, DNS, network routing, and firewall rules.

`I712` — Client Preflight Timeout¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: The target endpoint did not respond within the configured timeout.

Lösung: Increase timeout if appropriate, then verify endpoint health and latency.

`I713` — Client Preflight Resource Not Found¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: The configured resource does not exist or cannot be resolved.

Lösung: Create/verify the resource (for example topic/table/bucket) and retry.

`I714` — Client Preflight Unsupported Client¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: The client type is not part of the supported healthcheck contract.

Lösung: Use a supported client type or update the platform/runtime together.

`I715` — Client Preflight Authorization Failed¶

Client preflight failed for '{client_id}' ({kind}): {reason}

Warum: The credentials are valid but missing permissions for the configured resource.

Lösung: Grant required permissions and retry.

`I716` — Runtime Config Deprecated Key¶

Runtime key '{key}' is no longer supported. {replacement}

Warum: The runtime payload still contains a removed key from an older contract.

Lösung: Remove the deprecated key from platform_json and apply the documented migration path.

`I717` — Client Env Properties Missing¶

Missing descriptor-local environment properties file or client group in '{path}'

Warum: The runtime did not resolve a descriptor-local environment properties file or the requested client group was absent.

Lösung: Materialize descriptor-local env properties under conf/ with the required .. entries before running healthcheck or runtime. Use conf/local.env.properties in development (preferred) and conf/environment.env.properties otherwise.

`I718` — Object Storage Connection Failed¶

Connection to object storage service '{service}' failed: {reason}

Warum: The runtime could not establish or authenticate an object-storage connection.

Lösung: Verify endpoint availability, credentials, and network access, then retry.

`I801` — Task Key Missing Attrs¶

Must specify at least one attribute for element <{element_tag}> '{name}', such as '{attr_script}', '{attr_constant}', '{attr_values}', '{attr_generator}', '{attr_source}' or '{attr_type}'

Warum: A required configuration is missing in the task configuration.

Lösung: Provide the required configuration and retry.

`I802` — Task Subtask Invalid¶

Generate sub-task expected for {element_label}, but got {found_type}

Warum: The configuration value is invalid for the task configuration.

Lösung: Correct the configuration to a valid value or configuration.

`I803` — Task Statement Name Missing¶

Missing name for statement. Ensure the 'name' attribute is set before execution.

Warum: A required name for statement. Ensure the 'name' attribute is set before execution.

Lösung: Provide the required statement and retry.

`I804` — Task Array Script Element Type¶

Failed while evaluate script '{script}' of '{name}': expect array element datatypes in ({valid_types}), but got invalid datatype '{element_type}'

Warum: The system failed while evaluate script '{script}' of '{name}': expect array element datatypesin({valid_types}), but got invalid datatype '{element_type}'.

Lösung: Review the configuration and retry.

`I805` — Task Array Script Mixed Types¶

Failed while evaluate script '{script}' of '{name}': all elements in list must be the same data type

Warum: The system failed while evaluate script '{script}' of '{name}': all elements in list must be thesamedata type.

Lösung: Review the configuration and retry.

`I806` — Task Array Script Not List¶

expect datatype list of evaluated script '{script}' of '{name}', but got invalid datatype '{value_type}'

Warum: A value expected to be a list was not a list in the task configuration.

Lösung: Provide a list value for the script.

`I807` — Task Count Iteration Selector Requires DB¶

iterationSelector requires a database 'source' on nested

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I808` — Task Count Selector Unsupported Client¶

Using selector without count only supports DatabaseClient (MongoDB, Relational Database)

Warum: The task configuration specifies an unsupported client.

Lösung: Use a supported client or adjust the configuration.

`I809` — Task Count Missing¶

Cannot determine count for '{stmt_name}'. Provide an explicit count, a selector, or use a database-backed source that can be counted.

Warum: The system could not determine count for '{stmt_name}'. Provide an explicit count, a selector,oruse a database-backed source that can be counted.

Lösung: Provide the required configuration and retry.

`I810` — Task Count Not Int¶

Count of '{stmt_name}' is not an integer: {value}

Warum: A value expected to be an integer was not an integer in the task configuration.

Lösung: Provide a positive integer value.

`I811` — Task Unknown Converter¶

Unknown converter '{class_name}' for {element_label}. If this is a custom converter, ensure it is registered or use a fully qualified path.

Warum: The configuration references an unknown converter '{class_name}' for {element_label}. If this is acustomconverter, ensure it is registered or use a fully qualified path.

Lösung: Correct the configuration to a valid value or configuration.

`I812` — Task Script Error¶

Script error in {element_label}{descriptor}: {error}

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I813` — Task NestedKey Name Missing¶

Missing name for statement

Warum: A required name for statement.

Lösung: Provide the required configuration and retry.

`I814` — Task NestedKey Source Missing¶

Cannot load original data for '{name}'

Warum: The system could not load original data for '{name}'.

Lösung: Provide the required source and retry.

`I815` — Task NestedKey Script Type¶

Expect evaluated datatype of script '{script}' for '{name}' is 'list' or 'dict', but got invalid datatype: '{value_type}'

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I816` — Task NestedKey Result Type¶

Expect evaluated datatype of script '{script}' for '{name}' is 'list' or 'dict', but got invalid datatype: '{value_type}'

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I817` — Task NestedKey CSV Not List¶

CSV source '{source}' must resolve to a list of records for '{name}'

Warum: The configuration violates the requirement that CSV source '{source}' must resolve to a list of recordsfor '{name}'.

Lösung: Provide a list value for the CSV content.

`I818` — Task NestedKey Invalid Source¶

Invalid source '{source}' of '{name}'

Warum: The configuration provides an invalid source '{source}' of '{name}'.

Lösung: Correct the source to a valid value or configuration.

`I819` — Task NestedKey Dict Source Unsupported¶

Source of '{name}' having type 'dict' does not support format {source}

Warum: The task configuration specifies an unsupported configuration.

Lösung: Use a supported source or adjust the configuration.

`I820` — Task NestedKey Source Unsupported¶

Cannot load data from source '{source}' of '{name}'

Warum: The system could not load data from source '{source}' of '{name}'.

Lösung: Use a supported source or adjust the configuration.

`I821` — Task Key Subtask Invalid¶

Cannot execute subtask {task_name} of '{name}'

Warum: The system could not execute subtask {task_name} of '{name}'.

Lösung: Correct the configuration to a valid value or configuration.

`I822` — Task NestedKey Item Not Dict¶

Expect current product of '{name}' is a dictionary, but got invalid datatype: '{value_type}'

Warum: A value expected to be a dictionary was not a dictionary in the task configuration.

Lösung: Provide a dictionary value for the configuration.

`I823` — Task Execute Client Not Found¶

Client '{client_id}' not found for task. Check your project environment configuration.

Warum: The referenced client could not be found for the task configuration.

Lösung: Ensure the referenced client exists and the identifier/path is correct.

`I824` — Task Execute Script Not Found¶

Script file '{script_name}' not found in task workspace. Check your project environment configuration or uploaded script assets.

Warum: The referenced script could not be found for the task configuration.

Lösung: Ensure the referenced script exists and the identifier/path is correct.

`I825` — Task Key Script Invalid Type¶

'{name}' expects simple data type, but get invalid value '{value}' with type '{value_type}'

Warum: The script value is invalid for the task configuration.

Lösung: Correct the script to a valid value or configuration.

`I826` — Task Generate Iteration Selector Root¶

iterationSelector is not supported on root-level ; use nested or instead.

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I827` — Task Variable Unknown Client¶

Unknown database client '{client_id}' for '{name}'. Check your configuration or source_client attribute.

Warum: The configuration references an unknown database client '{client_id}' for '{name}'. Checkyour configuration or source_client attribute.

Lösung: Correct the client to a valid value or configuration.

`I828` — Task Variable Selector Only DB¶

'{name}': 'selector' only works with 'source' database (MongoDB, SQL)

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I829` — Task Variable Selector Missing¶

No selector value in '{name}'

Warum: A required configuration is missing in the task configuration.

Lösung: Provide the required configuration and retry.

`I830` — Task Variable Source Unsupported¶

Cannot get data from source '{source}' of '{name}'

Warum: The system could not get data from source '{source}' of '{name}'.

Lösung: Use a supported source or adjust the configuration.

`I831` — Task Variable Source Scripted Unsupported¶

sourceScripted only supports CSV or JSON data sources for '{name}'

Warum: The task configuration specifies an unsupported script.

Lösung: Use a supported source or adjust the configuration.

`I832` — Task Expression Eval Failed¶

Failed to evaluate expression '{expr}': {error}

Warum: The system failed to evaluate expression '{expr}': {error}.

Lösung: Fix the expression or script and retry.

`I833` — Task Common Subtask Invalid¶

Common sub-task expected for {element_label}, but got {found_type}

Warum: The configuration value is invalid for the task configuration.

Lösung: Correct the configuration to a valid value or configuration.

`I834` — Task Unknown Statement¶

Cannot create task for statement {statement_type}

Warum: The system could not create task for statement {statement_type}.

Lösung: Correct the statement to a valid value or configuration.

`I835` — Task Converter Registry Missing¶

Missing converter registrations for: {missing}

Warum: A required converter registrations for: {missing}.

Lösung: Provide the required configuration and retry.

`I836` — Task Values Invalid¶

Invalid values list for <{element_tag}> '{name}': {values}

Warum: The configuration provides an invalid values list for <{element_tag}> '{name}': {values}.

Lösung: Correct the configuration to a valid value or configuration.

`I837` — Task Weighted Source Invalid¶

Data source of {element_label} must be type of: 'wgt.csv'

Warum: The configuration violates the requirement that Data source of {element_label} must be type of: 'wgt.csv'.

Lösung: Correct the source to a valid value or configuration.

`I838` — Task Pattern Missing¶

Pattern is missing for <{element_tag}> '{name}'

Warum: A required pattern is missing in the task configuration.

Lösung: Provide the required pattern and retry.

`I839` — Task Generation Mode Unknown¶

Cannot find data generation mode for <{element_tag}> '{name}'

Warum: The system could not find data generation mode for <{element_tag}> '{name}'.

Lösung: Correct the configuration to a valid value or configuration.

`I840` — Task Converter Failed¶

Failed to generate data for <{element_tag}> '{name}': {error}

Warum: The system failed to generate data for <{element_tag}> '{name}': {error}.

Lösung: Review the configuration and retry.

`I841` — Task Type Cast Failed¶

Failed to cast value '{value}' to type '{data_type}' for <{element_tag}> '{name}': {error}

Warum: The system failed to cast value '{value}' to type '{data_type}' for <{element_tag}> '{name}': {error}.

Lösung: Review the configuration and retry.

`I842` — Task Datatype Invalid¶

Failed to convert datatype for <{element_tag}> '{name}'. Expect datatype {expected} but get '{data_type}'

Warum: The system failed to convert datatype for <{element_tag}> '{name}'. Expect datatype {expected} butget'{data_type}'.

Lösung: Correct the configuration to a valid value or configuration.

`I843` — Task Reference Unsupported Source¶

Reference '{name}' requires a configured relational or MongoDB source, or a .wgt.csv/.wgt.ent.csv project file

Warum: The reference source is neither a supported configured client nor a weighted project file.

Lösung: Use a relational or MongoDB source id, or provide a .wgt.csv/.wgt.ent.csv project file.

`I844` — Task Reference No Data¶

No data found for reference '{name}'

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I845` — Task Reference Unique Too Few¶

Cannot generate {requested} unique values - only {available} available for reference '{name}'

Warum: The system could not generate {requested} unique values - only {available} available for reference '{name}'.

Lösung: Review the configuration and retry.

`I846` — Task Reference Iterator Not Initialized¶

Iterator was not properly initialized for reference '{name}'

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I847` — Task Object Storage Unsupported Type¶

Unsupported object storage type '{object_storage_type}'

Warum: The configuration uses an unsupported object storage type '{object_storage_type}'.

Lösung: Use a supported object storage configuration or adjust the configuration.

`I848` — Task MP Platform Unsupported¶

Multiprocessing platform '{mp_platform}' of '{stmt_name}' is not supported

Warum: The mpPlatform value is not supported by the runtime.

Lösung: Use one of fork, spawn, or forkserver (or omit to use the system default).

`I849` — Task Generate Product Not Dict Source¶

Generate product must be a dictionary, but got {value_type} for statement '{stmt_name}'. If this comes from Kafka with format='string', switch to format='json' or wrap the value into a dict at the source.

Warum: The configuration violates the requirement that Generate product must be a dictionary, but got {value_type}forstatement '{stmt_name}'. If this comes from Kafka with format='string', switch to format='json' or wrapthevalue into a dict at the source.

Lösung: Provide a dictionary value for the source.

`I850` — Task Generate Product Not Dict Template¶

Template resolution result must be a dictionary, but got {value_type} for statement '{stmt_name}'

Warum: The configuration violates the requirement that Template resolution result must be a dictionary, butgot{value_type} for statement '{stmt_name}'.

Lösung: Provide a dictionary value for the template file.

`I851` — Task Generate Product Not Dict Script¶

Source script evaluated result must be a dictionary, but got {value_type} for statement '{stmt_name}'

Warum: The configuration violates the requirement that Source script evaluated result must be a dictionary, butgot{value_type} for statement '{stmt_name}'.

Lösung: Provide a dictionary value for the script.

`I852` — Task Generate Product Not Dict Converter¶

Generate product must be a dictionary after converters, but got {value_type} for statement '{stmt_name}'

Warum: The configuration violates the requirement that Generate product must be a dictionary after converters, butgot{value_type} for statement '{stmt_name}'.

Lösung: Provide a dictionary value for the configuration.

`I853` — Task Iteration Selector Not String¶

iteration_selector must be a string

Warum: The configuration violates the requirement that iteration_selector must be a string.

Lösung: Set the iteration selector to a string value.

`I854` — Task DB Table Unresolved¶

Could not resolve source entity/table name

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I855` — Task Entity Not Found¶

Entity name '{entity_name}' not found in the XML model

Warum: The referenced entity could not be found for the task configuration.

Lösung: Ensure the referenced entity exists and the identifier/path is correct.

`I856` — Task Variable Eval Failed¶

Failed to evaluate '{name}': {error}

Warum: The system failed to evaluate '{name}': {error}.

Lösung: Fix the expression or script and retry.

`I857` — Task Descriptor Dir Missing¶

Descriptor directory is required for '{name}'

Warum: A required script is missing in the task configuration.

Lösung: Provide the required script and retry.

`I858` — Task Scripting Context Missing¶

Scripting API is only available during expression evaluation

Warum: The scripting API was used outside of expression evaluation.

Lösung: Call scripting helpers only inside expression evaluation contexts.

`I859` — Task Scripting Product Name Invalid¶

product_name must be a non-empty string

Warum: The configuration violates the requirement that product_name must be a non-empty string.

Lösung: Correct the script to a valid value or configuration.

`I860` — Task Scripting Pagination Invalid¶

skip must be >= 0 and limit must be > 0

Warum: Pagination parameters are invalid (skip < 0 or limit <= 0).

Lösung: Provide skip >= 0 and limit > 0.

`I861` — Task Encoding Invalid¶

Invalid encoding name '{encoding}'

Warum: The encoding name is not recognized by Python.

Lösung: Use a valid encoding name such as utf-8 or latin-1.

`I862` — Task AMA Unresolved Placeholders¶

AMA output contains unresolved placeholders in {scope}: {tokens}

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I863` — Task ML Empty Dataset¶

Empty dataset for ml-train '{name}' (source='{source}')

Warum: A required configuration is empty in the task configuration.

Lösung: Provide a non-empty configuration and retry.

`I864` — Task Weighted Source Parse Failed¶

Invalid weighted source file '{name}' for {element_label}: {error}

Warum: The configuration provides an invalid weighted source file '{name}' for {element_label}: {error}.

Lösung: Fix the input format and retry.

`I865` — Task Weighted Entity Weight Column Missing¶

Weighted entity source '{name}' is missing weight column '{weight_column}' for {element_label}

Warum: A required weight values is missing in the task configuration.

Lösung: Provide the required weight values and retry.

`I866` — Task Entity Invalid Format¶

Invalid entity '{entity}' for {element_label}: expected 'schema.table' or 'table'

Warum: The configuration provides an invalid entity '{entity}' for {element_label}: expected 'schema.table'or'table'.

Lösung: Correct the entity to a valid value or configuration.

`I867` — Task Weighted Entity Empty¶

Weighted entity source '{name}' is empty for {element_label}

Warum: A required weight values is empty in the task configuration.

Lösung: Provide a non-empty weight values and retry.

`I868` — Task Weighted Entity No Weight Values¶

Weighted entity source '{name}' has no usable weight values for {element_label} (column '{weight_column}')

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I869` — Task Variable No Data¶

No data available for {element_label}

Warum: An error occurred during task configuration.

Lösung: Review the configuration and retry.

`I870` — Task Dynamic Pattern Not Allowed¶

Attribute '{attribute}' does not support {{{{expr}}}} (DYNAMIC) pattern; use {{expr}} (CACHED) or a literal value

Warum: A DYNAMIC pattern ({{expr}}) was used where it is not supported.

Lösung: Use {expr} (CACHED) or a literal value for the attribute.

`I871` — Task Nested Source Dynamic Requires Count¶

Nested '{stmt_name}' uses a dynamic source expression. Provide an explicit count or ensure the source is stable at setup time. Details: {error}

Warum: A nested generate uses a dynamic source expression, which requires a stable count.

Lösung: Provide an explicit count or ensure the source is stable at setup time.

`I872` — Task Nested Source URI Dynamic Unsupported¶

Nested '{stmt_name}' does not support dynamic sourceUri expressions. sourceUri is resolved in the root context; use a literal value.

Warum: sourceUri was provided as a dynamic expression for a nested generate.

Lösung: Use a literal sourceUri value resolved at the root context.

`I873` — Task Execute SQL Failed¶

Failed to execute SQL script '{script_name}' on client '{client_id}': {error_type}{error_code_hint}{error_category_hint}: {error}

Warum: SQL execution failed while running the task against the configured client.

Lösung: Review client configuration, SQL statement, and database permissions before retrying.

`I874` — Task Reference Query Failed¶

Failed to resolve reference '{name}' from source '{source_type}' and sourceKey '{source_key}': {error_type}{error_code_hint}{error_category_hint}: {error}

Warum: Database query failed while resolving values for a task.

Lösung: Review sourceType/sourceKey, SQL identifier validity, and database permissions before retrying.

`I875` — Task Reference Single Weighting Multi Field¶

Reference '{name}' uses single-column weighting source '{source}' with {target_count} mapped fields. Use exactly one field for '.wgt.csv' or switch to '.wgt.ent.csv' for tuple references.

Warum: Single-column weighting files cannot represent multi-column tuple references.

Lösung: Map exactly one target field for '.wgt.csv' or use '.wgt.ent.csv' with mappings.

`I876` — Task Reference Unique Duplicates¶

Reference '{name}' requires business-unique values but source has {duplicates} duplicate rows ({unique_available} unique values from {total_rows} rows). Set platform_json 'reference_unique_duplicate_policy' to warning/skip/ignore if deduplication is acceptable.

Warum: The unique reference source contains duplicate business tuples while strict duplicate policy is enabled.

Lösung: Deduplicate the source values, or change reference_unique_duplicate_policy to warning/skip/ignore when duplicates are expected.

`I877` — Task Unresolved Placeholder¶

Unresolved placeholder '{placeholder}' in {context_label} for {element_label}. The expression '{expr}' is being treated as a literal string, not as supported DATAMIMIC interpolation

Warum: A placeholder-like token remained unresolved in a context that does not support inline interpolation.

Lösung: Use a supported full-value expression/property pattern or materialize the value before this step.

`I878` — Task Unsupported Expression Global¶

Unsupported expression global '{name}' in expression '{expr}' for {context_label}. DATAMIMIC expressions only support whitelisted SAFE_GLOBALS helpers and context variables

Warum: The expression references a Python builtin or helper that is not part of the DATAMIMIC expression contract.

Lösung: Use a supported SAFE_GLOBALS helper or move the logic into trusted Python loaded via .

`I879` — Task Entity Constructor Invalid¶

Invalid entity constructor '{expr}' for {element_label}: {cause}

Warum: The entity constructor does not match the supported DATAMIMIC constructor syntax.

Lösung: Use a valid constructor like EntityName(...) with supported literal values or supported expression forms.

`I880` — Task Inline Placeholder In Python Expression¶

Placeholder-like token(s) {tokens} are not supported inside Python expression '{expr}' for {context_label}. Use bare variable names without braces.

Warum: The expression mixes DATAMIMIC-style placeholder braces into a raw Python expression.

Lösung: Remove the braces and reference the variables directly, or materialize the values before this step.

`I881` — Task Expression Type Contract Mismatch¶

Expression mixes string and numeric values in '{expr}' for {context_label}. Referenced values: {names_hint}. Cast explicitly or fix the source/type contract.

Warum: The expression relies on implicit type coercion across incompatible runtime values.

Lösung: Cast the value explicitly in the expression or fix the upstream source/type contract.

`I882` — Task Variable Invalid Storage Mode¶

Invalid storage mode '{value}' for '{name}'. Allowed values: 'value', 'data', 'iterator'.

Warum: The 'storage' attribute on the element contains an unrecognised value.

Lösung: Set storage to one of: 'value', 'data', 'iterator', or remove the attribute to use the default.

`I883` — Time-Series Bad Start¶

Invalid time-series configuration: {detail}

Warum: The 'start' attribute is not a valid ISO 8601 datetime.

Lösung: Set start to an ISO 8601 datetime, e.g. '2026-01-01T00:00:00Z'.

`I884` — Time-Series Bad End¶

Invalid time-series configuration: {detail}

Warum: The 'end' attribute is not a valid ISO 8601 datetime.

Lösung: Set end to an ISO 8601 datetime, e.g. '2026-01-02T00:00:00Z'.

`I885` — Time-Series Bad Interval¶

Invalid time-series configuration: {detail}

Warum: The 'interval' attribute is not a valid ISO 8601 duration.

Lösung: Set interval to an ISO 8601 duration, e.g. 'PT1H'.

`I886` — Time-Series End Not After Start¶

Invalid time-series configuration: {detail}

Warum: The 'end' attribute is not strictly after the 'start' attribute.

Lösung: Set end to a datetime strictly after start.

`I887` — Time-Series Interval Too Fine¶

Invalid time-series configuration: {detail}

Warum: The 'interval' duration is non-positive, sub-microsecond, or a months/years Duration.

Lösung: Set interval to a positive constant-length duration of at least 1us, e.g. 'PT1S'.

`I888` — Time-Series Namespace Collision¶

is not allowed inside a time-series : 'ts' is reserved for the time-iterator namespace (ts.now/ts.step/ts.series). Rename the variable, e.g. 'ts_meta'.

Warum: A would shadow the reserved time-iterator namespace.

Lösung: Rename the variable to something other than 'ts', e.g. 'ts_meta'.

`I889` — Time-Series Incomplete Config¶

Time-series attributes start/end/interval must be set together; missing: {missing}

Warum: Only some of the time-series attributes start/end/interval were provided.

Lösung: Provide all three attributes (start, end, interval) or none of them.

`I890` — Task Key Weights Length¶

<{element_tag} '{name}'> needs one weight per value: {weight_count} weights vs {value_count} values

Warum: The number of entries does not match the number of values.

Lösung: Provide exactly one weight per value, or remove weights for a uniform pick.

`I891` — Task Key Weights Not Numeric¶

<{element_tag} '{name}'> weights must be comma-separated numbers, got {weights}

Warum: A entry could not be parsed as a number.

Lösung: Use comma-separated numeric weights, e.g. weights="0.7,0.2,0.1".

`I892` — Task Key Weights Negative Or Zero Sum¶

<{element_tag} '{name}'> weights must be non-negative with a positive sum

Warum: A entry is negative or all weights sum to zero.

Lösung: Use non-negative weights with at least one positive value.

`I893` — Task Key Unique Exhausted¶

<{element_tag} '{name}' unique> exhausted: only {distinct_count} distinct values, reduce count or add more values.

Warum: A was asked for more records than it has distinct values.

Lösung: Reduce the generated count or provide more distinct values.

`I894` — Task Execute Bash Failed¶

failed (exit {exit_code}): {detail}

Warum: The shell command run by returned a non-zero exit status.

Lösung: Fix the shell command or its environment; inspect the reported stderr/exit code.

`I895` — Task Assert Failed¶

failed: condition {condition} is not true{extra}

Warum: An invariant did not hold for the setup context or a generated record.

Lösung: Correct the generation logic or the assertion so the condition holds.

`I896` — Task Reference Ordered Exhausted¶

Ordered reference '{name}' exhausted after {count} rows; add cyclic="true" to wrap, or reduce the generated count.

Warum: A non-cyclic distribution="ordered" was walked past its last candidate.

Lösung: Add cyclic="true" to wrap, or reduce the generated count.

`I897` — Parser Execute Type Unresolved¶

: cannot infer execution type from the file extension; set an explicit type=.

Warum: The uri has no recognised extension and no explicit type= was given.

Lösung: Set type= (python, sql, or bash), or use a uri with a recognised extension.

`I898` — Task Source Unique Exhausted¶

Cannot generate {requested} unique values for {label}: only {available} distinct available.

Warum: A source-backed unique selection was asked for more records than the source has distinct rows.

Lösung: Reduce the generated count or provide more distinct source rows.

`I899` — Task Source Sample Exhausted¶

Cannot sample {requested} rows without replacement for {label}: only {available} available.

Warum: A reservoir (sample-without-replacement) selection was asked for more rows than the source has.

Lösung: Reduce the generated count, provide more source rows, or add cyclic="true" to wrap.

`I900` — Task Distribution Unsupported On Database Source¶

distribution='{distribution}' is not supported on a database/mongo source ({source}) yet: it needs the whole pool, which the sharded DB read path cannot provide.

Warum: weighted/reservoir/stratified sample over the WHOLE pool; the DB/mongo read is keyset-sharded for mass data and cannot materialize a global pool, so the distribution would be silently ignored.

Lösung: Use a file source (CSV/JSON) for these distributions, or ordered/random on the DB source.

`I901` — Operation Execution Failed¶

Operation '{target}' failed: {error}

Warum: An error occurred during operation execution.

Lösung: Review the configuration and retry.

`I902` — Operation Template Variables Missing¶

Template variable(s) {missing} not found. Available variables: {available}. Template path: {template_path}

Warum: A required template is missing in the operation execution.

Lösung: Provide the required template file and retry.

`I903` — Operation Mongo Duplicate Key¶

Mongo {operation} failed on collection '{collection}': duplicate key error ({reason})

Warum: A duplicate key was detected while performing the operation execution.

Lösung: Ensure values are unique or adjust constraints, then retry.

`I904` — Operation Mongo Write Not Allowed¶

Mongo {operation} not allowed for collection '{collection}': {reason}

Warum: An error occurred during operation execution.

Lösung: Review the configuration and retry.

`I905` — Operation Mongo Validation Failed¶

Mongo {operation} validation failed for collection '{collection}': {reason}

Warum: An error occurred during operation execution.

Lösung: Review the configuration and retry.

`I906` — Operation Mongo Namespace Not Found¶

Mongo {operation} namespace '{namespace}' not found

Warum: The referenced Mongo could not be found for the operation execution.

Lösung: Ensure the referenced Mongo namespace exists and the identifier/path is correct.

`I907` — Operation Read-Only Write Blocked¶

Operation '{target}' blocked by read-only datasource mode: {reason}

Warum: A write operation was attempted against a datasource configured for read-only access.

Lösung: Disable read-only mode or use a writable datasource for update/delete/insert operations.

`I908` — Task Source Weight Column Invalid¶

Cannot apply distribution='weighted' for {label}: {reason}.

Warum: The weight_column is missing from the source rows, non-numeric, negative, or sums to zero.

Lösung: Point weightColumn at a numeric, non-negative column with a positive sum.

`I909` — Task Source Stratify Column Invalid¶

Cannot apply distribution='stratified' for {label}: {reason}.

Warum: The stratifyBy column is missing from the source rows.

Lösung: Point stratifyBy at a column that exists in every source row.

`I910` — Task Variable Storage Unresolvable Source¶

source '{source}' has no stable pool to materialize (not a file/database/memstore source).

Warum: storage= requires a source that resolves to a materializable pool up front; '{source}' resolves dynamically at task runtime (e.g. it names another ).

Lösung: Remove storage= or point source at a file, database table, or memstore.

`I911` — Task While Loop Max Iterations Exceeded¶

exceeded max_iterations={max_iterations}: condition '{condition}' never became false (possible infinite loop).

Warum: The loop condition remained true after reaching the maximum iteration limit.

Lösung: Verify the loop condition and ensure it eventually becomes false, or increase maxIterations if needed.

`I912` — Generate Offset Unsupported for Memstore¶

'{stmt_name}': offset= is only supported for file sources, not memstore '{source_str}'.

Warum: The offset attribute cannot be used with memstore/product sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a file source instead of memstore.

`I913` — Generate Offset Unsupported for Database Client¶

'{stmt_name}': offset= is only supported for file sources, not database client '{source_str}' - use a selector with an SQL/Mongo skip instead.

Warum: The offset attribute cannot be used with database client sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a file source instead of a database client.

`I914` — Generate Offset Unsupported for Template Source¶

'{stmt_name}': offset= is only supported for file sources, not template source '{source_str}'.

Warum: The offset attribute cannot be used with template sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a file source instead of a template.

`I915` — Generate Offset Unsupported for Kafka¶

'{stmt_name}': offset= is only supported for file sources, not Kafka source '{source_str}'.

Warum: The offset attribute cannot be used with Kafka sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a file source instead of Kafka.

`I916` — Generate Offset Unsupported for Object Storage¶

'{stmt_name}': offset= is only supported for file sources, not object storage source '{source_str}'.

Warum: The offset attribute cannot be used with object storage sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a project file source instead of object storage.

`I917` — Generate Offset Unsupported for ML Model¶

'{stmt_name}': offset= is only supported for file sources, not ML model source '{source_str}'.

Warum: The offset attribute cannot be used with ML model sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a file source instead of an ML model.

`I918` — Source Memstore Product Invalid¶

Invalid memstore product name '{product_name}' requested for read. Expected pattern: {pattern}

Warum: The effective memstore product name (from sourceEntity/targetEntity/type/name) is empty or contains characters outside the allowed charset - Redis SCAN treats '*', '?', '[', ']' as glob wildcards, so an unchecked product name could match unrelated products instead of the exact one.

Lösung: Use a plain alphanumeric product name (letters, digits, '.', '_', '-' only) and retry.

`I919` — State Machine Transition Unknown Attribute¶

has unknown attribute(s) {attrs}, expected only 'from', 'to', 'weight'

Warum: A child of declared an attribute outside 'from'/'to'/'weight'.

Lösung: Remove the unexpected attribute(s) or correct the spelling.

`I920` — State Machine Transition Missing From/To¶

requires non-empty 'from' and 'to' attributes

Warum: A child of is missing 'from' and/or 'to'.

Lösung: Provide both 'from' and 'to' on every .

`I921` — State Machine Transition Weight Not Numeric¶

weight must be numeric, got '{weight}'

Warum: A value could not be parsed as a float.

Lösung: Use a numeric weight, e.g. weight="0.9".

`I922` — State Machine Transition Weight Not Positive¶

weight must be > 0, got {weight}

Warum: A value is zero or negative.

Lösung: Use a strictly positive weight (or omit weight= for the default of 1.0).

`I923` — State Machine No Transitions¶

must declare at least one child

Warum: A element has zero children.

Lösung: Add at least one child.

`I924` — State Machine Duplicate Id¶

Duplicate : a state machine with this id is already registered

Warum: Two or more elements declare the same id=.

Lösung: Use a distinct id= for each .

`I925` — State Machine Id Collides With Generator¶

collides with a builtin generator class name

Warum: A matches an existing builtin generator class name.

Lösung: Choose an id= that does not match any registered generator class name.

`I926` — RDBMS Delete Source and Target Must Differ¶

RDBMS delete target '{target_entity}' on client '{client_id}' is the same table as source '{source_entity}'

Warum: Deleting rows from the table being paged as a source can shift later pages and silently skip records.

Lösung: Use a separate source and target table, or stage the source rows before running the delete operation.

`I927` — RDBMS Delete Selector Source Must Be Provable¶

Cannot prove that RDBMS delete target '{target_entity}' on client '{client_id}' is isolated from selector '{selector}'

Warum: A complex or dynamic selector on the same RDBMS connection can read the delete target and shift later pages, silently skipping records.

Lösung: Use a simple single-table selector for a separate source table, or materialize the source rows in a staging table before running the delete operation.

`I928` — Database Operation Intent Is Invalid¶

Operation '{target}' is unsafe or ambiguous: {reason}. Migration: {migration}

Warum: The descriptor does not distinguish selective deletion, clearing records, and dropping the database object strongly enough for a destructive operation.

Lösung: Use the explicit delete, clear, or drop target described in the migration guidance.

`I929` — Source RabbitMQ Client Missing¶

RabbitMQ source requested but client was None

Warum: RabbitMQ source loading requires a configured RabbitMQ importer client instance.

Lösung: Provide a valid RabbitMQ importer client and retry.

`I930` — Generate Offset Unsupported for RabbitMQ¶

'{stmt_name}': offset= is only supported for file sources, not RabbitMQ source '{source_str}'.

Warum: The offset attribute cannot be used with RabbitMQ sources; it only applies to file-based sources.

Lösung: Remove the offset attribute, or use a file source instead of RabbitMQ.

`I931` — Source RabbitMQ Client Unsupported API¶

RabbitMQ client '{client_type}' must implement consume_iter_message(count)

Warum: The configured RabbitMQ client does not implement the required consume API contract.

Lösung: Use a RabbitMQ importer client that implements consume_iter_message.

`I932` — Source RabbitMQ TLS Failed¶

RabbitMQ TLS/SSL handshake failed for queue '{queue}': {reason}

Warum: The RabbitMQ importer failed the TLS/SSL handshake while reading messages.

Lösung: Verify RabbitMQ certificates, trust chain, hostname validation, and TLS settings.

`I933` — Source RabbitMQ Authentication Failed¶

RabbitMQ authentication failed for queue '{queue}': {reason}

Warum: The RabbitMQ importer could not authenticate with the configured credentials.

Lösung: Verify the RabbitMQ user and password for the importer connection.

`I934` — Source RabbitMQ Authorization Failed¶

RabbitMQ authorization failed for queue '{queue}': {reason}

Warum: The RabbitMQ importer is authenticated but lacks permission to read the queue.

Lösung: Grant the configured user read access to the virtual host and queue.

`I935` — Source RabbitMQ Network Failed¶

RabbitMQ network connectivity failed for queue '{queue}': {reason}

Warum: The RabbitMQ importer could not reach the configured broker endpoint.

Lösung: Verify RabbitMQ host, port, DNS, routing, and firewall connectivity.

`I936` — Source RabbitMQ Timeout¶

RabbitMQ read timed out for queue '{queue}': {reason}

Warum: The RabbitMQ source operation exceeded its timeout while reading messages.

Lösung: Retry the operation or tune RabbitMQ connection and heartbeat timeout settings.

`I937` — Source RabbitMQ Queue Not Found¶

RabbitMQ queue '{queue}' not found or inaccessible: {reason}

Warum: The configured RabbitMQ queue does not exist or cannot be accessed by the importer.

Lösung: Verify the queue exists and the configured user can access it.

`I938` — Source RabbitMQ Read Failed¶

RabbitMQ source read failed for queue '{queue}': {reason}

Warum: The RabbitMQ importer encountered an unclassified failure while reading messages.

Lösung: Inspect RabbitMQ broker/client logs and importer configuration, then retry.

`I939` — Export RabbitMQ TLS Failed¶

RabbitMQ TLS/SSL handshake failed for exchange '{exchange}': {reason}

Warum: The RabbitMQ exporter failed the TLS/SSL handshake while publishing messages.

Lösung: Verify RabbitMQ certificates, trust chain, hostname validation, and TLS settings.

`I940` — Export RabbitMQ Authentication Failed¶

RabbitMQ authentication failed for exchange '{exchange}': {reason}

Warum: The RabbitMQ exporter could not authenticate with the configured credentials.

Lösung: Verify the RabbitMQ user and password for the exporter connection.

`I941` — Export RabbitMQ Authorization Failed¶

RabbitMQ authorization failed for exchange '{exchange}': {reason}

Warum: The RabbitMQ exporter is authenticated but lacks permission to publish to the exchange.

Lösung: Grant the configured user write access to the virtual host and exchange.

`I942` — Export RabbitMQ Network Failed¶

RabbitMQ network connectivity failed for exchange '{exchange}': {reason}

Warum: The RabbitMQ exporter could not reach the configured broker endpoint.

Lösung: Verify RabbitMQ host, port, DNS, routing, and firewall connectivity.

`I943` — Export RabbitMQ Timeout¶

RabbitMQ publish timed out for exchange '{exchange}': {reason}

Warum: The RabbitMQ export operation exceeded its timeout while publishing messages.

Lösung: Retry the operation or tune RabbitMQ connection, heartbeat, and blocked-connection timeouts.

`I944` — Export RabbitMQ Exchange Not Found¶

RabbitMQ exchange '{exchange}' not found or inaccessible: {reason}

Warum: The configured RabbitMQ exchange does not exist or cannot be accessed by the exporter.

Lösung: Verify the exchange exists and the configured user can access it.

`I945` — Export RabbitMQ Message Unroutable¶

RabbitMQ could not route a message through exchange '{exchange}' with routing key '{routing_key}': {reason}

Warum: The broker returned a mandatory message because no queue binding matched its routing key.

Lösung: Create a matching queue binding or correct the exchange and routing key.

`I946` — Export RabbitMQ Write Failed¶

RabbitMQ write failed through exchange '{exchange}' with routing key '{routing_key}': {reason}

Warum: The RabbitMQ exporter encountered an unclassified publish or shutdown failure.

Lösung: Inspect RabbitMQ broker/client logs and exporter configuration, then retry.

`I947` — Source RabbitMQ Option Unsupported¶

RabbitMQ source '{source}' does not support {option}={value}. Supported behavior: {supported}.

Warum: The requested source-selection option cannot be preserved by bounded RabbitMQ queue consumption.

Lösung: Remove the unsupported option or use one of the listed RabbitMQ source behaviors.

`I948` — Source Kafka Option Unsupported¶

Kafka source '{source}' does not support {option}={value}. Supported behavior: {supported}.

Warum: The requested source-selection option cannot be preserved by bounded Kafka topic consumption.

Lösung: Remove the unsupported option or use the listed Kafka source behavior.

`I949` — Source ML Model Option Unsupported¶

ML model source '{source}' does not support {option}={value}. Supported behavior: {supported}.

Warum: The requested source-selection option cannot be preserved by generated ml:// model samples.

Lösung: Remove the unsupported option and use bounded ordered ML model generation.

`I950` — Operate Control Template Missing¶

Operate control CSV '{csv_path}' has no non-blank template value in row(s): {rows}

Warum: Each non-blank control row needs a template reference before operations can be applied.

Lösung: Set the 'template' column for every control row or remove the malformed row.

`I951` — Operate Template Format Unsupported¶

Operate template '{template}' has unsupported suffix '{suffix}'; supported suffixes: {supported}

Warum: The operate executor has format-specific XML and JSON implementations only.

Lösung: Use an .xml or .json template file.

`I952` — Source Project Path Outside Workspace¶

Project file '{source}' is outside workspace root '{workspace_root}'

Warum: An explicit file source resolves outside the bound project workspace.

Lösung: Use a file:// path below the project workspace root.

`W001` — Distribution Parameter Ignored¶

<{element} distribution='{distribution}'>: {param}='{value}' is ignored — only distribution='{consumer}' uses it; running the '{distribution}' selection without it.

Warum: A parameter was set alongside a distribution that does not consume it.

Lösung: Remove the parameter, or switch to the distribution that uses it.

`W002` — Echo Placeholder Unresolved¶

: could not evaluate diagnostic placeholder text '{value}'{error_clause}; logging the literal text instead.

Warum: The echo text referenced a name or expression that is not available in the current runtime scope.

Lösung: Fix the placeholder expression, or remove it if the echo is only diagnostic output.

`W003` — Legacy Destructive Operation Intent¶

target '{legacy_target}' resolves to '{effective_target}' under the DATAMIMIC 3.5 compatibility contract. This form is deprecated and will be removed in 5.0. Migration: {migration}

Warum: The descriptor uses the overloaded 3.5 delete target instead of declaring delete, clear, or drop intent explicitly.

Lösung: Replace the legacy target shape with the explicit target named in the migration message.

`W004` — Deprecated XML Attribute Ignored¶

<{element}> attribute '{attribute}' in descriptor '{descriptor}' is deprecated and ignored; execution continues. {migration}

Warum: The descriptor uses a known legacy attribute that no longer controls execution.

Lösung: Follow the migration hint when updating the model. Removing the attribute is not required to run it.

`W005` — Deprecated Memstore Declaration Ignored¶

in descriptor '{descriptor}' is deprecated and ignored; execution continues. The built-in Memstore needs no declaration. Use target='mem' to write and source='mem' with sourceEntity to read. This declaration does not create a custom source or target ID.

Warum: The descriptor declares a Memstore even though the runtime provides the built-in mem source and target.

Lösung: Remove the declaration when updating the model; keep its data-producing and data-reading steps.

`W006` — Memstore Dataset Selected Through type¶

<{element}> attribute type='{entity}' in descriptor '{descriptor}' is read as sourceEntity='{entity}'; execution continues. Use sourceEntity for dataset selection and keep type for list or dict; if you meant a container, check the spelling of type.

Warum: A memstore dataset is selected through type instead of sourceEntity.

Lösung: Move the dataset name to sourceEntity; reserve type for list or dict.

Referenz der Fehlercodes¶

E001 — Invalid Dataset¶

E002 — Invalid Locale¶

E003 — Datetime Conversion Failed¶

E004 — Entity Init Failed¶

E005 — Rule Eval Failed¶

E006 — Invalid Source¶

E007 — Export Config¶

E008 — Include Error¶

E009 — Generator Config¶

E010 — Condition Eval Failed¶

E011 — Parser Validation¶

E012 — Client Config¶

E013 — Task Config¶

E014 — Operation Error¶

E015 — Runtime Config¶

I101 — Source File Not Found¶

I102 — Source Invalid CSV¶

I103 — Source Invalid CSV Header¶

I104 — Source Invalid JSON¶

I105 — Source Invalid XML¶

I106 — Source Invalid NDJSON¶

I107 — Source JSON Root Invalid¶

I108 — Source XML Root Invalid¶

I109 — Source Unsupported File Type¶

I110 — Source JSON Array Not Acceptable¶

I111 — Source JSON Object Mode Unsupported¶

I112 — Source JSON Wrappable Required¶

I113 — Source Template Empty¶

I114 — Source Template Not Found¶

I115 — Source Template Invalid XML¶

I116 — Source Expr Not String¶

I117 — Source Expr Item Not String¶

I118 — Source Expr Nested Not String¶

I119 — Source Expr Eval Failed¶

I120 — Source Client Unsupported¶

I121 — Source Unknown Client¶

I122 — Source Unknown¶

I123 — Source Object Storage Bucket Missing¶

I124 — Source Object Storage Bucket Attr Missing¶

I125 — Source Object Storage URI Missing¶

I126 — Source Object Storage Object Not Found¶

I127 — Source Object Storage Invalid Payload¶

I128 — Source Object Storage Unsupported Type¶

I129 — Source DB Query Client Missing¶

I130 — Source DB Table Client Missing¶

I131 — Source Memstore Task ID Missing¶

I132 — Source Unsupported Type¶

I133 — Source Item Unsupported¶

I134 — Source File Path Not String¶

I135 — Source Index Required¶

I136 — Source ML Unknown¶

I137 — Source Project Ctx Missing¶

I138 — Source Project Path Outside Descriptor¶

I139 — Source Project Descriptor Dir Symlink¶

I140 — Source Project Symlink Escape¶

I141 — Source Project Path Non Local¶

I142 — Source DB Table Not Found¶

I143 — Source DB Column Not Found¶

I144 — Source DB Query Syntax¶

I145 — Source DB Permission Denied¶

I146 — Source DB Type Mismatch¶

I147 — Source DB Column Ambiguous¶

I148 — Source DB Schema Not Found¶

I149 — Source DB Function Not Found¶

I150 — Source Mongo Selector Invalid¶

I151 — Source Mongo Selector Unsupported¶

I152 — Source Mongo Permission Denied¶

I153 — Source Mongo Namespace Not Found¶

I154 — Source Mongo Query Invalid¶

I155 — Source DB Connection Failed¶

I156 — Source DB Timeout¶

I157 — Source DB Deadlock¶

I158 — Source Object Storage Client Missing¶

I159 — Source Kafka Client Missing¶

I160 — Source Return Type Unsupported¶

I161 — Source Massive Mode Fallback Blocked¶

I162 — Source DB Route Unsupported Client¶

I163 — Source DB Query Or Table Required¶

I164 — Source Kafka Client Unsupported API¶

`E001` — Invalid Dataset¶

`E002` — Invalid Locale¶

`E003` — Datetime Conversion Failed¶

`E004` — Entity Init Failed¶

`E005` — Rule Eval Failed¶

`E006` — Invalid Source¶

`E007` — Export Config¶

`E008` — Include Error¶

`E009` — Generator Config¶

`E010` — Condition Eval Failed¶

`E011` — Parser Validation¶

`E012` — Client Config¶

`E013` — Task Config¶

`E014` — Operation Error¶

`E015` — Runtime Config¶

`I101` — Source File Not Found¶

`I102` — Source Invalid CSV¶

`I103` — Source Invalid CSV Header¶

`I104` — Source Invalid JSON¶

`I105` — Source Invalid XML¶

`I106` — Source Invalid NDJSON¶

`I107` — Source JSON Root Invalid¶

`I108` — Source XML Root Invalid¶

`I109` — Source Unsupported File Type¶

`I110` — Source JSON Array Not Acceptable¶

`I111` — Source JSON Object Mode Unsupported¶

`I112` — Source JSON Wrappable Required¶

`I113` — Source Template Empty¶

`I114` — Source Template Not Found¶

`I115` — Source Template Invalid XML¶

`I116` — Source Expr Not String¶

`I117` — Source Expr Item Not String¶

`I118` — Source Expr Nested Not String¶

`I119` — Source Expr Eval Failed¶

`I120` — Source Client Unsupported¶

`I121` — Source Unknown Client¶

`I122` — Source Unknown¶

`I123` — Source Object Storage Bucket Missing¶

`I124` — Source Object Storage Bucket Attr Missing¶

`I125` — Source Object Storage URI Missing¶

`I126` — Source Object Storage Object Not Found¶

`I127` — Source Object Storage Invalid Payload¶

`I128` — Source Object Storage Unsupported Type¶

`I129` — Source DB Query Client Missing¶

`I130` — Source DB Table Client Missing¶

`I131` — Source Memstore Task ID Missing¶

`I132` — Source Unsupported Type¶

`I133` — Source Item Unsupported¶

`I134` — Source File Path Not String¶

`I135` — Source Index Required¶

`I136` — Source ML Unknown¶

`I137` — Source Project Ctx Missing¶

`I138` — Source Project Path Outside Descriptor¶

`I139` — Source Project Descriptor Dir Symlink¶

`I140` — Source Project Symlink Escape¶

`I141` — Source Project Path Non Local¶

`I142` — Source DB Table Not Found¶

`I143` — Source DB Column Not Found¶

`I144` — Source DB Query Syntax¶

`I145` — Source DB Permission Denied¶

`I146` — Source DB Type Mismatch¶

`I147` — Source DB Column Ambiguous¶

`I148` — Source DB Schema Not Found¶

`I149` — Source DB Function Not Found¶

`I150` — Source Mongo Selector Invalid¶

`I151` — Source Mongo Selector Unsupported¶

`I152` — Source Mongo Permission Denied¶

`I153` — Source Mongo Namespace Not Found¶

`I154` — Source Mongo Query Invalid¶

`I155` — Source DB Connection Failed¶

`I156` — Source DB Timeout¶

`I157` — Source DB Deadlock¶

`I158` — Source Object Storage Client Missing¶

`I159` — Source Kafka Client Missing¶

`I160` — Source Return Type Unsupported¶

`I161` — Source Massive Mode Fallback Blocked¶

`I162` — Source DB Route Unsupported Client¶

`I163` — Source DB Query Or Table Required¶

`I164` — Source Kafka Client Unsupported API¶

`I165` — Source Return Payload Type Mismatch¶