Sebastian Oelke

@elpic Is this still an issue for you? If so, I need a bit more information here. It's hard to guess what might be going wrong. What is your setup/configuration?

What backend are you using with devise async? When your backend wants to process the email and deliver it, does it throw an exception?

Have you tried https://github.com/mhfs/devise-async#troubleshooting ?

Hmm, ok. Then I am a bit out of ideas...

@maia I currently do not have the time to investigate deeply... Do you have a minimal setup that I could use to investigate further?

@jjb When using delayed job it is possible to further delay the running of a job by using something like `run_at: -> { 5.minutes.from_now }`. Perhaps you can use this...

Did I get this right: 1. You increment the reminder count (`changed? == true`). 2. Then, you call `send_confirmation_instructions` which generates a new `confirmation_token` and saves the record (`changed? ==...

@jjb Ah, I see my mistake, now. :-) Hmm, at least you could do ``` ruby class User def remind increment!(:email_confirmation_reminder_count) send_confirmation_instructions end end ``` Or is there a reason...

@jjb Well, no need for excuses. It's your decision. ;-) In the end, I don't know what exactly happens with this gem. As mentioned in https://github.com/mhfs/devise-async/issues/64 there might be the...

@gingerlime Hey, I do not have enough experience with Active Job and this particular case to tell the truth. But, yes, this issue could also occur when using Active Job....