If a Smart Contract isn't executing properly, an exception may have been raised. These are visible in the service logs.

Services that can trigger contract execution:

- vault-postings-processor

- contract-schedule-executor

- plan-schedule-executor

- vault-account-processor

- contract-post-posting-processor

Services directly involved in contract execution:

- smart-contracts

- contract-executor

- supervisor-contract-executor

Services that contract execution may depend on, either for requirements and resources or directives:

- contract-schedule-last-run-times

- kernel-balances

- scheduler

- vault-account

- vault-posting

- vault-postings-processor-internal

- workflow-processor

The Operations Dashboard also includes error information in the Ledgers for failed payments or posting instruction batches. The account detail page has details of failed schedules and transfers.