Bug: Spoke does not handle Bandwidth password errors cleanly #2231
Comments
|
Thank you for sharing your notes! I have forwarded this issue to our engineering team. As for the monitoring the Heroku Logs so that you can be notified when there is a problem. Jeff from AFL-CIO suggested the following: "we use the corologix addon for heroku to capture/analyze logs, but I’ve also totally replaced the spoke logging with a json logger (pino), so YMMV" I'd be happy to meet with you soon to work on getting corologix add-on information loaded to your instance (and doubly prepare documentation that can be added to the Spoke.) |
|
Hey @rhayhow , thanks for reporting this issue! It's definitely important for there to be some sort of indication that there's an error when Bandwidth authentication fails. Side note: Are you currently using an "API Access" user in the Spoke configuration? An "API Access" user won't be prompted to change their password every 90 days, whereas a regular user with access to the Bandwidth dashboard will be prompted to change their password every 90 days: https://support.bandwidth.com/hc/en-us/articles/360061927414-Changes-to-the-Bandwidth-Dashboard-UI-API-user-access-methods I recommend for you to use an "API Access" user in your Spoke configuration to avoid the mandatory 90-day password change and potential interruptions in texting. |
|
Thank you @crayolakat! Hey @rhayhow, I think it's less about whether or not you are using the API and more about Spoke having the functionality to synch credential updates between your Bandwidth Account and your Spoke Account if those credentials are connected to a user setting called "API User." It is my belief that this access comes with your Bandwidth Account. When we read your issue ticket with the Engineering Team, we were able to identify two separate issues
Do you have any questions or concerns about this plan? |
Describe the bug
I changed my Bandwidth password (at their prompting) and forgot to update the password saved in the Spoke configuration page for my organization. Later in the day we had a texting party where we sent ~88,000 texts before anyone started wondering if something was wrong. We did not see any replies or opt-outs which is highly unlikely after sending that many texts. I didn't see any errors in the campaign console, which is also odd because we almost always get a few errors.
This led me to look at the Heroku logs for the Spoke app where I saw errors indicating that the user attempting to send texts was not authenticated. However there was no indication in the Spoke application (either to texters or administrators) that there was a problem. I know that I have seen error message in Spoke before like "There was a problem sending the message," but for some reason this type of error didn't cause that message.
To resolve the issue I updated my password in the Spoke configuration page and the errors went away.
To Reproduce
Steps to reproduce the behavior:
Configure a Spoke instance to use Bandwidth and confirm that it is working. Use the suggested username/password pair in the Spoke Settings page.
Change your Bandwidth password here https://passport.bandwidth.com/forgot-password
Try to send texts and observe errors in Heroku log console
Also observe that no errors appear either in the Texter context or in the Campaign page for that campaign
Expected behavior
An error message would be displayed to the Texter, "There was a problem sending your message." and the error would appear in the Campaign page for that campaign.
Screenshots
See above
Platform (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: