Skip to main content

UserCodeFaultKind

What went wrong, at the granularity an operator would alert on and a developer would fix. One kind per distinguishable remedy: an expression timeout and a watchdog termination are both "ran too long" and are kept apart because one rolls back a transaction and the other kills a worker thread.

enum UserCodeFaultKind {
  EXPRESSION_TIMEOUT
  GAS_EXHAUSTED
  CALL_LIMIT_EXCEEDED
  EXPRESSION_ERROR
  WASM_TRAP
  FUEL_EXHAUSTED
  MEMORY_EXCEEDED
  WATCHDOG_TERMINATED
  MODULE_LOAD_FAILED
  BINDING_MISMATCH
  RESPONSE_TOO_LARGE
  SANDBOX_POISONED
  WORKER_EXIT
  HOST_CALL_FAILED
  UNKNOWN_HOST_FUNCTION
  INTERNAL_ERROR
  DB_OPS_EXCEEDED
  EGRESS_BUDGET_EXCEEDED
  STATE_WRITE_BUDGET_EXCEEDED
  RATE_LIMIT_EXCEEDED
  QUOTA_EXHAUSTED
  CONTRACT_VALIDATION_FAILED
  PLATFORM_BUSY
  CIRCUIT_OPEN
  DISABLED_BY_POLICY
  NOTIFICATION_UNDELIVERABLE
}

Values

`UserCodeFaultKind.EXPRESSION_TIMEOUT`

`UserCodeFaultKind.GAS_EXHAUSTED`

`UserCodeFaultKind.CALL_LIMIT_EXCEEDED`

`UserCodeFaultKind.EXPRESSION_ERROR`

`UserCodeFaultKind.WASM_TRAP`

`UserCodeFaultKind.FUEL_EXHAUSTED`

`UserCodeFaultKind.MEMORY_EXCEEDED`

`UserCodeFaultKind.WATCHDOG_TERMINATED`

`UserCodeFaultKind.MODULE_LOAD_FAILED`

`UserCodeFaultKind.BINDING_MISMATCH`

`UserCodeFaultKind.RESPONSE_TOO_LARGE`

`UserCodeFaultKind.SANDBOX_POISONED`

`UserCodeFaultKind.WORKER_EXIT`

`UserCodeFaultKind.HOST_CALL_FAILED`

`UserCodeFaultKind.UNKNOWN_HOST_FUNCTION`

`UserCodeFaultKind.INTERNAL_ERROR`

`UserCodeFaultKind.DB_OPS_EXCEEDED`

`UserCodeFaultKind.EGRESS_BUDGET_EXCEEDED`

`UserCodeFaultKind.STATE_WRITE_BUDGET_EXCEEDED`

`UserCodeFaultKind.RATE_LIMIT_EXCEEDED`

`UserCodeFaultKind.QUOTA_EXHAUSTED`

`UserCodeFaultKind.CONTRACT_VALIDATION_FAILED`

`UserCodeFaultKind.PLATFORM_BUSY`

`UserCodeFaultKind.CIRCUIT_OPEN`

`UserCodeFaultKind.DISABLED_BY_POLICY`

`UserCodeFaultKind.NOTIFICATION_UNDELIVERABLE`

Member Of

UserCodeFaultRecord object ● userCodeFaults query ● UserCodeFaultSummaryEntry object

Values
Member Of