I was updating part of the UI and making some api calls to adjust some elements.
The api call was failing. I thought it was because my local environment didn’t have the correct settings. I tried adjusting the event handler to debug with no luck.
In the meantime my slack was sending notifications that there were errors on my local environment. I knew this but thought this must have been working before so it must be something on my end.
I finally decided to try on our test environment and sure enough the same error occurred and I received the same slack message. I decided to look into the message further and then realized it was a legit backend error.

Going to the error bucket I could see this was the exact same error I experienced locally and on test.

I quickly created a new ticket to track the error where the next backend engineer would be able to easily reproduce this and fix the issue. I brought it up in stand up the next day and a collegue said its a quick fix.

Instead of pulling in a backend developer to help me debug locally or them try on their machine I could send the Railtown link to them and they could easily confirm the problem.