Hey I really don't like the new simulator. If there is an endpoint error the simulator just does nothing, nor does it register the error with cloudwatch. I would type out the invocation name and would get 0 response, it was as if the request was never sent. When I would then check the cloudwatch logs there would be nothing reflecting a request either. If I swap to the old version and try the simulator, it will make the request and respond with an error. This will then register in Cloud watch and point me right to where the break is. Missing this functionality is a MAJOR issue and should be fixed ASAP. I will not use the new version of the simulator until this is fixed as it completely bungles debugging and it's absolutely mystifying why this is in the current state
Jens Kohl commented
Do you eventually have some sort of ad blocker activated? Deactivating it for the simulator did the trick for me. Now I get the same error messages I got from the old simulator.