Serverless Functions ... now you see me, now you don't!

Hello HS Devs! for some context before I dive in, I built some serverless functions on the original 2023.1 CMS Development version and had things running very well. I have now upgraded all of them to use 2023.2, and have successfully made the required changes and deployed them. Here is where I am running into some issues. I have 6 different endpoints that have all exhibited the following behavior at some point in the past week. The behavior I am speaking of is getting a returned error that looks like this:

The odd thing is that this very same call succeeded 4 minutes prior, with no changes having been made to that endpoint.

One clue may be that this behavior seems to happen after a deployment where a different serverless function was changed.
Happy to help troubleshoot this however you’d like!

Thanks,

-Mike

Hi, @Mike_H99 :waving_hand: Welcome to our community! Thanks for your question.

I’d like to invite some of our community members to the conversation — hey @Phil_Vallender @ChrisoKlepke @Teun do you have any recent experience you can share with @Mike_H99? Or share some troubleshooting strategies you might use for a case like this?

Thank you very much! — Jaycee

With the help of the Product team, this has been resolved along with other unidentified serverless issues