Lambda function, clicking "Test" does nothing today but has worked for months

Is this the first time you are testing the lambda function, if so, can you please check if you have created the test event and while testing that test event payload is being used.

Hi Donald,

Here are a few concrete next steps that can help pinpoint why the Test button shows no response:

1. Check your browser’s Developer Tools (Console/Network) for errors Open Developer Tools → Console/Network, click Test, and see if any JavaScript or HTTP errors appear. If errors show up, the Lambda console UI likely failed to load part of its components.

2. Check CloudTrail to confirm whether the Invoke API was called Go to CloudTrail → Event history, filter by:

   • Event name: Invoke or InvokeFunction
   • Time: the moment you clicked Test If no Invoke event appears, the console UI never sent the request.

3. Check CloudWatch Logs for a new invocation Go to CloudWatch Logs → /aws/lambda/<function-name> and look for a new log stream at the time of the test.

   • CloudTrail shows Invoke but CloudWatch has no logs → function error or permission issue
   • Both show nothing → the UI did not trigger execution

4. As another data point, you can also check whether the same behavior occurs when logging in with a different IAM user or role. If a different IAM identity shows the same “no response” behavior, the issue is very likely isolated to the console UI rather than your specific user session.

Koji

This issue where clicking "Test" on your Lambda function doesn't trigger any action is something that other AWS users have experienced as well. There are several potential causes and solutions to explore:

1. Region Check: First, verify you're in the correct AWS region where your Lambda function was created. Lambda functions are region-specific, so if you're viewing a different region, your function might not appear or respond correctly.

2. Browser/Device Issue: Try accessing your Lambda function from a different browser or device to rule out any local issues. Sometimes clearing cache and cookies isn't enough to resolve browser-related problems.

3. Console UI Issue: There might be a temporary issue with the AWS Lambda console interface. This can sometimes happen and prevent the test button from working properly.

4. Permissions: Even though you've been able to run this function before, check if there have been any recent changes to your IAM permissions that might affect your ability to execute Lambda functions.

5. Service Health: Check the AWS Service Health Dashboard to see if there are any ongoing issues or outages with Lambda in your region.

If the issue persists after trying these steps, the most effective solution would be to contact AWS Support. You can open a case under the "Account and billing" category, which can be done free of charge. AWS Support can investigate account-specific issues that might be causing this problem with your Lambda console.

In the meantime, you could try alternative methods to invoke your function, such as using the AWS CLI or AWS SDK if your workflow allows for it.
Sources
Not able to see my lambda functions | AWS re:Post
Root User - Lambda Functions are Gone! | AWS re:Post