Elixir.Bamboo.PostmarkAdapter.ApiError: :timeout
https://sentry.io/code-corps/code-corps-api/issues/284027328/
Elixir.Bamboo.PostmarkAdapter.ApiError: :timeout
File "lib/bamboo/postmark_adapter.ex", line 51, in Bamboo.PostmarkAdapter.deliver/2
File "lib/bamboo/mailer.ex", line 123, in Bamboo.Mailer.deliver_now/3
File "lib/code_corps/services/forgot_password.ex", line 12, in CodeCorps.Services.ForgotPasswordService.forgot_password/1
File "web/controllers/password_controller.ex", line 10, in CodeCorps.PasswordController.forgot_password/2
File "web/controllers/password_controller.ex", line 1, in CodeCorps.PasswordController.action/2
...
(3 additional frame(s) were not displayed)
(Bamboo.PostmarkAdapter.ApiError) :timeout
As far as I can tell, this was an actual timeout. PostmarkAdapter simply passes out the reason provided by hackney in an {:error, reason} tuple, so the :timeout atom was sent by hackney.
Are our hackney settings in staging/production good enough? I seem to recall a contributor mentioning we should do something with our pool_size in some issue.
This might have been in a Sentry repo that we saw the pool size comment. Maybe we can go spelunking for that.
Found the comment, it was in the analytics library:
https://github.com/stueccles/analytics-elixir/issues/7#issuecomment-293410628