ecotone-resiliency

Configure retry strategies, error channels, and dead-letter handling for Ecotone message processing.

2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ecotoneframework/skills --skill ecotone-resiliency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecotone-resiliency
Source: https://github.com/ecotoneframework/skills/tree/main/skills/ecotone-resiliency
Command: npx skills add https://github.com/ecotoneframework/skills --skill ecotone-resiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ecotone resiliency features provide robust handling of message processing failures with configurable retries, error channels, dead-letter queues, and the outbox pattern to guarantee delivery and structured failure handling.

Core Features & Use Cases

  • Retry strategies with configurable backoffs (fixed, exponential, with max delay)
  • Error handling via ErrorHandlerConfiguration with optional dead-letter channel
  • FinalFailureStrategy to define behavior when retries are exhausted
  • Outbox pattern using a DBAL-backed channel for atomic storage
  • Enterprise options like InstantRetry and per-endpoint error routing

Quick Start

Set up a resiliency configuration that wires a retry policy, an error channel, and an optional dead-letter channel, then enable the outbox pattern for guaranteed delivery.

Frequently Asked Questions about ecotone-resiliency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure retry strategies for message processing in Ecotone?

You configure retry strategies in Ecotone using RetryTemplateBuilder to define fixed, exponential, or max delay backoffs for message-driven workloads experiencing transient failures.

What is the outbox pattern and how does it guarantee message delivery?

The outbox pattern guarantees delivery by using DbalBackedMessageChannelBuilder for atomic storage, ensuring messages are safely persisted within a database transaction before processing.

How do I handle dead-letter routing when retries are exhausted?

Dead-letter routing is handled by configuring ErrorHandlerConfiguration with a dead-letter channel. FinalFailureStrategy defines the exact behavior when retries are exhausted, routing failed messages to the dead-letter queue.

Can I set up per-endpoint error routing and instant retries in Ecotone?

Yes, Ecotone supports enterprise options like InstantRetry for immediate retry attempts and per-endpoint error routing to direct failures to specific error channels based on the message source.

What is the best way to structure failure handling for asynchronous messaging?

The best way to structure failure handling is wiring a retry policy with RetryTemplateBuilder, an error channel via ErrorHandlerConfiguration, and a dead-letter queue for guaranteed delivery and structured failure management.