I guess that's one of the advantages of serverless - by definition there can be no unrelated error in the state beyond the request (because there is none), exce

I guess that's one of the advantages of serverless - by definition there can be no unrelated error in the state beyond the request (because there is none), except for the infrastructure definition itself. But a misconfig there you'll always see in form of an error happening at calling the particular resource - at least I haven't seen anything else yet.