anyone else using Script for migrations and getting it stuck in checking deploy status? The lambda failed however the stack remains stuck

It's likely failing when invoked, this is always a big pain to test. I usually go to the AWS console and invoke manually

is this some kind of limitation on aws's side with custom resources? seems weird that the stack never fails because it doesn't recognize the lambda failed

They take 30min to fail usually