My guess is with such a big source migration the AWS lambda source is somehow cached or still propagating in the background - I guess my question is if there is a way to monitor when the function really is available? I thought I could trust the Netlify functions UI, but there was a good 20-30 minutes where my identity-signup handler was totally broken. It finally started working again as expected after I shipped 1 or 2 more builds with some extra logging in the functions as an insanity check - but this could be bad news bears if the site has high signup traffic!
I monitor my functions with various logs, so I know they weren’t having any issues. Again, it is almost like they just weren’t being called.
Wondering if anyone else had ever seen such behavior after a big function migration.