@joseph-benguira
Solved... and I think I know why, very edge case π
I had a callback at the very end of my function handler, after a bunch of async/await stuff.
Lambda has a context object:
"callbackWaitsForEmptyEventLoop"
From their docs:
"Set to false to send the response right away when the callback runs, instead of waiting for the Node.js event loop to be empty. If this is false, any outstanding events continue to run during the next invocation."
Anyway, removing the callback at the end of the function worked. I think lambda was executing the callback without waiting for the inner await'd functions to finish, which killed the running processes and prevented the updates from happening.
Does "Try" run with a different context object than a scheduled function?