We don't know why this happens. Some time ago it happend because the mailing was triggered before the record was saved to the database.
This resulted in sidekiq loading the Billing which was still in documented state and thus decided not to change the state to delivered.
We need to investigate whether this happens now. Maybe there is some caching going on besides the initial timing issue.
We don't know why this happens. Some time ago it happend because the mailing was triggered before the record was saved to the database. This resulted in sidekiq loading the
Billingwhich was still in documented state and thus decided not to change the state to delivered.We need to investigate whether this happens now. Maybe there is some caching going on besides the initial timing issue.