Katherine Wu comments

Results 5 comments of


                                            Katherine Wu

Pending batches expiring in 5 months, not 30 days

Yup, thanks @raybaxter ours looks just like that as well.

Child batches with enqueued jobs don't prevent parent batches from completing

Sure, this is what it looks like: ```ruby # frozen_string_literal: true class StagerJob < ApplicationJob sidekiq_options queue: :within_1_hour, retry_for: 24.hours, unique_for: 10.minutes NotWithinParentBatchError = Class.new(StandardError) def self.start_workflow_for(foo_id:) foobar_record = FooBar.find_by(foo_id:...

Child batches with enqueued jobs don't prevent parent batches from completing

We _do_ have `Sidekiq.transactional_push!`! However I don't understand how that applies to this situation with batch jobs--I thought batch jobs just always push at the end of the jobs block?...

Child batches with enqueued jobs don't prevent parent batches from completing

I've put in a `rescue Sidekiq::Batch::Immutable` in our implementation for resetting the data to be able to start the workflow over again from the beginning.

Child batches with enqueued jobs don't prevent parent batches from completing

I appreciate that, although unfortunately, probably not something that I will realistically get to in the near future. I plan to keep an eye on these batches and see how...