Apache Pekko Documentation onErrorContinue
Type to start searching
    apache/pekko
    apache/pekko
    • Security Announcements
      • Receiving Security Advisories
      • Reporting Vulnerabilities
      • Security Related Documentation
    • Release Notes
      • Release Notes (1.3.x)
      • Release Notes (1.2.x)
      • Release Notes (1.1.x)
      • Release Notes (1.0.x)
    • Getting Started Guide
      • Introduction to Apache Pekko
      • Why modern systems need a new programming model
      • How the Actor Model Meets the Needs of Modern, Distributed Systems
      • Overview of Apache Pekko libraries and modules
      • Introduction to the Example
      • Part 1: Actor Architecture
      • Part 2: Creating the First Actor
      • Part 3: Working with Device Actors
      • Part 4: Working with Device Groups
      • Part 5: Querying Device Groups
    • General Concepts
      • Terminology, Concepts
      • Actor Systems
      • What is an Actor?
      • Supervision and Monitoring
      • Actor References, Paths and Addresses
      • Location Transparency
      • Apache Pekko and the Java Memory Model
      • Message Delivery Reliability
      • Configuration
      • Default configuration
    • Actors
      • Introduction to Actors
      • Actor lifecycle
      • Interaction Patterns
      • Handling responses in Scala 3
      • Fault Tolerance
      • Actor discovery
      • Routers
      • Stash
      • Behaviors as finite state machines
      • Coordinated Shutdown
      • Dispatchers
      • Mailboxes
      • Testing
      • Coexistence
      • Style guide
      • Learning Pekko Typed from Classic
    • Cluster
      • Cluster Usage
      • Cluster Specification
      • Cluster Membership Service
      • Phi Accrual Failure Detector
      • Distributed Data
      • Cluster Singleton
      • Cluster Sharding
      • Cluster Sharding concepts
      • Sharded Daemon Process
      • Multi-DC Cluster
      • Distributed Publish Subscribe in Cluster
      • Reliable delivery
      • Serialization
      • Serialization with Jackson
      • Multi JVM Testing
      • Multi Node Testing
      • Artery Remoting
      • Classic Remoting (Deprecated)
      • Split Brain Resolver
      • Coordination
      • Choosing Pekko Cluster
    • Persistence (Event Sourcing)
      • Event Sourcing
      • Replicated Event Sourcing
      • CQRS
      • Style Guide
      • Snapshotting
      • Testing
      • EventSourced behaviors as finite state machines
      • Schema Evolution for Event Sourced Actors
      • Apache Persistence Query
      • Persistence Query for LevelDB
      • Persistence Plugins
      • Persistence - Building a storage backend
      • Replicated Event Sourcing Examples
    • Persistence (Durable State)
      • Durable State
      • Style Guide
      • CQRS
      • Persistence Query
    • Streams
      • Module info
      • Introduction
      • Streams Quickstart Guide
      • Design Principles behind Apache Pekko Streams
      • Basics and working with Flows
      • Working with Graphs
      • Modularity, Composition and Hierarchy
      • Buffers and working with rate
      • Context Propagation
      • Dynamic stream handling
      • Custom stream processing
      • Futures interop
      • Actors interop
      • Reactive Streams Interop
      • Error Handling in Streams
      • Working with streaming IO
      • StreamRefs - Reactive Streams over the network
      • Pipelining and Parallelism
      • Testing streams
      • Substreams
      • Streams Cookbook
      • Configuration
      • Operators
    • Discovery
      • Module info
      • How it works
      • Discovery Method: DNS
      • Discovery Method: Configuration
      • Discovery Method: Aggregate multiple discovery methods
      • Migrating from Pekko Management Discovery (before 1.0.0)
    • Utilities
      • Event Stream
      • Logging
      • Circuit Breaker
      • Futures patterns
      • Extending Apache Pekko
    • Other Apache Pekko modules
      • Pekko HTTP
      • Pekko gRPC
      • Pekko Connectors
      • Pekko Kafka Connector
      • Pekko Projections
      • Cassandra Plugin for Pekko Persistence
      • JDBC Plugin for Pekko Persistence
      • R2DBC Plugin for Pekko Persistence
      • Apache Pekko Management
    • Package, Deploy and Run
      • Packaging
      • Operating a Cluster
      • Deploying
      • Rolling Updates
    • Project Information
      • Binary Compatibility Rules
      • Scala 3 support
      • Downstream upgrade strategy
      • Modules marked “May Change”
      • IDE Tips
      • Immutability using Lombok
      • Apache Pekko in OSGi
      • Rolling Updates and Versions
      • Issue Tracking
      • Licenses
      • License Report
      • Frequently Asked Questions
      • Books and Videos
      • Example projects
      • Project
    • Pekko Classic
      • Classic Actors
      • Classic Clustering
      • Classic Networking
      • Classic Utilities
    • Migration Guides
      • Migration from Akka to Apache Pekko
      • Migration from Apache Pekko 1.0.x to 1.1.x
    • onErrorContinue
      • Signature
      • Description
      • Reactive Streams semantics
    • link Apache Software Foundation
    • link License
    • link Security
    • link Privacy
    • link Events
    • link Donate
    • link Thanks
    • onErrorContinue
      • Signature
      • Description
      • Reactive Streams semantics

    onErrorContinue

    Continues the stream when an upstream error occurs.

    Error handling

    Signature

    Source.onErrorContinueSource.onErrorContinue Flow.onErrorContinueFlow.onErrorContinue

    Description

    Continues the stream when an upstream error occurs.

    Reactive Streams semantics

    emits element is available from the upstream

    backpressures downstream backpressures

    completes upstream completes or upstream failed with exception this operator can’t handle

    Cancels when downstream cancels

    Edit this page
    1.3.0
    Previous onErrorComplete
    Next onErrorResume
    Copyright © 2011-2022 Lightbend, Inc. Apache Pekko, Pekko, and its feather logo are trademarks of The Apache Software Foundation.