generated: '2026-07-21' method: searched source: https://docs.sentio.xyz/docs/error-codes scope: processor / subgraph runtime error codes (SDK 3.x+); prefixed ERRxxx in error messages categories: - range: 1xx category: system who_acts: Sentio (internal, auto-retried) - range: 2xx category: driver who_acts: Sentio (data pipeline, usually transient) - range: 3xx category: processor who_acts: Consumer (fix processor code/config/schema, re-upload) - range: 4xx category: billing who_acts: Consumer (plan limits — upgrade or reduce usage) error_count: 53 codes: - code: ERR100 name: System category: system responsibility: sentio description: An unexpected internal error occurred in the runtime. Retried automatically; contact support if it persists. - code: ERR101 name: Need Upgrade category: system responsibility: sentio description: The processor requires capabilities that the currently running runtime version does not support yet. The platform reschedules it automatically. - code: ERR102 name: Out Of Memory category: system responsibility: sentio description: The runtime ran out of memory while processing. Often transient; if it keeps recurring, try reducing the amount of data held per handler call. - code: ERR200 name: Call Processor Failed category: driver responsibility: sentio description: Communication with the processor runtime failed (timeout, broken stream, or unexpected response). Usually transient. - code: ERR201 name: Reset WASM Instance Failed category: driver responsibility: sentio description: Failed to reset the WebAssembly instance between executions (subgraph processors). - code: ERR202 name: WASM Error category: driver responsibility: sentio description: The WebAssembly runtime reported an internal error while executing the processor (subgraph processors). - code: ERR203 name: Get Contract Start Block Failed category: driver responsibility: sentio description: Failed to resolve the creation / start block of a contract or account from the chain. - code: ERR204 name: Fetch Data Failed category: driver responsibility: sentio description: Failed to fetch on-chain data (blocks, transactions, logs, etc.) from the data source. - code: ERR205 name: Subgraph Eth Call Failed category: driver responsibility: sentio description: An `eth_call` issued by a subgraph handler failed at the RPC level (node error, timeout). - code: ERR206 name: Subgraph IPFS Cat Failed category: driver responsibility: sentio description: An `ipfs.cat` request issued by a subgraph handler failed. - code: ERR207 name: Invalid Checkpoint Data category: driver responsibility: sentio description: The processing checkpoint data was inconsistent or corrupted. - code: ERR208 name: Save Checkpoint Failed category: driver responsibility: sentio description: Failed to persist the processing checkpoint to storage. - code: ERR209 name: Quota Service Error category: driver responsibility: sentio description: Failed to communicate with the quota / billing service while checking usage. - code: ERR210 name: Clean Time Series Data Failed category: driver responsibility: sentio description: Failed to clean up previously written metric / event data (for example during reprocessing). - code: ERR211 name: Save Time Series Data Failed category: driver responsibility: sentio description: Failed to write metric / event log data to storage. - code: ERR212 name: Send Webhook Data Failed category: driver responsibility: sentio description: Failed to deliver webhook messages emitted by the processor. - code: ERR213 name: Init Entity Failed category: driver responsibility: sentio description: Failed to initialize entity storage for the processor's schema. - code: ERR214 name: Clean Entity Data Failed category: driver responsibility: sentio description: Failed to clean up previously written entity data (for example during reprocessing). - code: ERR215 name: Save Entity Data Failed category: driver responsibility: sentio description: Failed to write entity data to storage. - code: ERR216 name: Get Entity From DB Failed category: driver responsibility: sentio description: Failed to read an entity from storage. - code: ERR217 name: List Entity From DB Failed category: driver responsibility: sentio description: Failed to list entities from storage. - code: ERR218 name: Invalid Entity Data category: driver responsibility: sentio description: Entity data read from or written to storage was invalid or corrupted. - code: ERR300 name: Unexpected Processor Config category: processor responsibility: consumer description: The processor configuration does not match the data being processed — for example, data arrived for which no handler is registered. - code: ERR301 name: Invalid Entity Schema category: processor responsibility: consumer description: The entity schema (`schema.graphql`) is invalid or uses unsupported constructs. - code: ERR302 name: Processor Configs Has Diff category: processor responsibility: consumer description: Multiple instances of the same processor produced different configurations. This usually means the processor setup code is non-deterministic (e.g. uses random values or timestamps when registering handlers). - code: ERR303 name: Process Failed category: processor responsibility: consumer description: A handler threw an error at runtime — the most common error for bugs in handler code (null access, failed assertions, unhandled exceptions). Check the error detail and stack trace, and see [Troubleshooting](https://docs.sentio.xyz/docs/troubleshooting). - code: ERR304 name: Call WASM Export Function Failed category: processor responsibility: consumer description: Calling an exported function of the subgraph WebAssembly module failed. - code: ERR305 name: WASM Init Failed category: processor responsibility: consumer description: The subgraph WebAssembly module failed to initialize. - code: ERR306 name: WASM Stack Overflow category: processor responsibility: consumer description: The subgraph handler overflowed the WebAssembly stack — usually caused by infinite or overly deep recursion. - code: ERR307 name: Create Template Failed category: processor responsibility: consumer description: Creating a template instance failed — for example, invalid parameters passed to template instantiation. - code: ERR308 name: Invalid Subgraph Manifest category: processor responsibility: consumer description: The subgraph manifest (`subgraph.yaml`) is invalid. - code: ERR309 name: Get Unknown Entity category: processor responsibility: consumer description: The handler tried to load an entity type that is not defined in the schema. - code: ERR310 name: List Unknown Entity category: processor responsibility: consumer description: The handler tried to list an entity type that is not defined in the schema. - code: ERR311 name: List Related Entity With Invalid Field category: processor responsibility: consumer description: The handler tried to look up related entities through a field that is not a relation field. - code: ERR312 name: Invalid List Entity Filter category: processor responsibility: consumer description: A `list` query used an invalid filter — for example, filtering on a field that does not exist or with an incompatible operator. - code: ERR313 name: Invalid Upsert Entity Request category: processor responsibility: consumer description: An entity upsert request was malformed — for example, missing the entity ID or required data. - code: ERR314 name: Upsert Unknown Entity category: processor responsibility: consumer description: The handler tried to upsert an entity type that is not defined in the schema. - code: ERR315 name: Invalid Update Entity Request category: processor responsibility: consumer description: An entity update request was malformed. - code: ERR316 name: Update Unknown Entity category: processor responsibility: consumer description: The handler tried to update an entity type that is not defined in the schema. - code: ERR317 name: Invalid Delete Entity Request category: processor responsibility: consumer description: An entity delete request was malformed. - code: ERR318 name: Delete Unknown Entity category: processor responsibility: consumer description: The handler tried to delete an entity type that is not defined in the schema. - code: ERR319 name: Update Immutable Entity category: processor responsibility: consumer description: The handler tried to modify an entity that is declared immutable in the schema. - code: ERR320 name: Invalid Entity Field Value category: processor responsibility: consumer description: An entity field value does not match its declared type — for example, wrong type, `null` for a non-nullable field, or a value out of range. - code: ERR321 name: Invalid Time Series Data category: processor responsibility: consumer description: A metric or event log record is invalid — for example, an invalid metric / label name or an unsupported value. See [Metrics](https://docs.sentio.xyz/docs/metrics) for naming rules. - code: ERR322 name: Time Series Data Schema Changed category: processor responsibility: consumer description: The same metric or event log was emitted with a conflicting schema — for example, the same field written with different data types. - code: ERR323 name: Too Many Webhook Msg Entity category: processor responsibility: consumer description: The processor emitted more webhook messages in one batch than allowed. - code: ERR324 name: Subgraph Eth Call With Invalid Param category: processor responsibility: consumer description: An `eth_call` issued by a subgraph handler used invalid parameters — for example, a malformed address or arguments that do not match the ABI. - code: ERR325 name: Processor Heap Overflow category: processor responsibility: consumer description: The processor exceeded its JavaScript heap limit and was terminated ("JavaScript heap out of memory"). Usually caused by holding too much data in memory — for example, accumulating large arrays, maps, or caches across handler calls. Reduce the amount of data kept in memory per handler. - code: ERR326 name: Too Many Metrics category: processor responsibility: consumer description: The processor created more distinct metrics (counters and gauges combined) than allowed. Usually caused by deriving metric names from unbounded values — for example, embedding an address or a token symbol in the metric name. Use a fixed set of metric names and put variable values in labels instead. - code: ERR327 name: Too Many Event Types category: processor responsibility: consumer description: The processor created more distinct event log types than allowed. Usually caused by deriving event names from unbounded values. Use a fixed set of event names and put variable values in event attributes instead. - code: ERR328 name: Too Many Time Series category: processor responsibility: consumer description: A single metric has more time series (distinct label combinations) than allowed, or the total number of time series across all metrics exceeded the limit. Avoid using unbounded values — such as block numbers, timestamps, or transaction hashes — as label values. - code: ERR329 name: Too Many Entity Types category: processor responsibility: consumer description: The entity schema defines more entity types (entities, interfaces, and aggregations) than allowed. Reduce the number of types defined in the GraphQL schema. - code: ERR400 name: Over Quota category: billing responsibility: consumer description: The project has exceeded the quota of its current plan and processing is paused. Upgrade the plan, or reduce usage (see [Cost Reduction](https://docs.sentio.xyz/docs/cost-reduction)).