Internal Server Error with new dependency

What I’m trying to do:
Add new dependency to apps with routes.

What I’ve tried and what’s not working:
I’ve tried across 2 accounts adding a new dependency (from my account and 3rd party) to new and old apps and every time after I add the new dependency routes beside the base URL start giving me various Internal Server Error codes.

Clone link:
share a copy of your app

Hi @duncan_richards12,

I just cloned your app, published it, and accessed its /test endpoint, and it worked just fine. I’m afraid we’ll need more detailed instructions on how to replicate this issue!

Alternatively, pasting at least one of those error codes would allow us to look up the error in our logs for more context.

2 Likes

:face_with_spiral_eyes: Ahh, it just stopped happening for me too. I guess maybe it was something intermitent… somewhere :person_shrugging:

Ok, so this just happened again when I added a new dependency to a rather large app of mine.

When I added this same dependency to another app of mine that’s only got a few bare forms, there’s no issue. This would certainly explain what you said here last month:

If I had to bet money, I would say this will resolve itself sometime in the next 24 hrs, but its also probably some weird bug in your system maybe.

Here are the last 2 error codes I received:

Internal server error: c9de815a7050
Internal server error: 1e4fa259b6b8

Aaaaand that turned out to be the case when I just checked. :thought_balloon: