Exception: Wurk::Limiter::Rescheduled

Inherits:

JobRetry::Skip

• Object
• RuntimeError
• JobRetry::Handled
• JobRetry::Skip
• Wurk::Limiter::Rescheduled

Defined in:

lib/wurk/limiter/server_middleware.rb

Overview

Control signal raised after a job has been rescheduled: the limiter has already re-enqueued it (via Client.push at Time.now + backoff), so the run is neither a success nor a failure. Subclassing JobRetry::Skip routes it through the existing "middleware re-pushed the job — ack cleanly, book no retry" contract: the retrier re-raises it untouched, the outer Batch middleware skips both acks (its rescue Handled re-raises), and the Processor acks the UnitOfWork. Returning normally instead would let the outer Batch onion ack success for a job that never ran. Internal only — not part of the Sidekiq drop-in surface.