#liam-curran_error
solemn obsidianBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1291737464503013377
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
vale breach
that's all we're receiving unfortunately, we haven't been able to replicate locally
It's only happening in our CI when running e2e tests
but locally it works fine and on production it works fine
but this functionality hasn't changed for us at all in a long time, so seems odd it's suddenly not working
mighty grotto
and you don't know which code triggered that error?
vale breach
sorry yep we do know but unfortunately don't have any logs coming out from it in our e2e tests
no error is coming up in the stacktrace when the error shows in the e2es
mighty grotto
I'm not sure how to help with just one string of an error message. if you can share more information about the error itself, or share the exact code that returned that error, then should be able to inevstiagte this.
vale breach
yep no problem - we'll try add some extra logging information so we can have better observability
thank you anyway
have a good weekend
mighty grotto
makes sense!