summaryrefslogtreecommitdiff
path: root/db/migrate/20201007140032_add_guest_token_to_subscriptions.rb
diff options
context:
space:
mode:
authorAlberto Vena <kennyadsl@gmail.com>2021-07-12 15:29:53 +0200
committerAlberto Vena <kennyadsl@gmail.com>2021-07-13 16:22:59 +0200
commitc9e26197b0abbe50b029c368017243314d572884 (patch)
tree751072edbfae746e21045bdc027606c48c2670d2 /db/migrate/20201007140032_add_guest_token_to_subscriptions.rb
parent662719693c9f369cd9176e432ab3d4a554822751 (diff)
Logs an error in the Rails logs when installment processing fails
At the moment, by default, all installment prceissing errors are swallowed and there's no way for a developer to understand what's happening. Of course they can create a custom handler with the processing_error_handler configuration provided but usually, when the first errors happen, it's too late and those errors are lost. We are not raising errors of this job because if there's a retry mechanism in place for Active Job, the installment will be reprocessed twice. Once by Active Job and once by the installment retry mechanism already provided by the extension. Logging to Rails.error is a middle-ground that allows to intercept the message of the exception. Still, creating a custom handler based on the bug tracker/exception handler used is the suggested option here.
Diffstat (limited to 'db/migrate/20201007140032_add_guest_token_to_subscriptions.rb')
0 files changed, 0 insertions, 0 deletions