CloudWatch Synthetics Canaries Bug

I am seeing the same error when creating CloudWatch Synthetics Canaries. It was fine if no Synthetics Canary exist, but once created one, the error will appear and no Canary listed

Then i went to the Overview tab and click on Running canaries it show my canaries in deleted state

I'm seeing exactly the same error. Clearing my cache, etc doesn't seem to fix the problem.

2 months is a long time for an obvious and annoying bug like this to stay on the dashboard. It impact the ability to use the service. I cannot see any results on the "List" page. The ability to find and edit Canaries is harder because of it. When editing Canaries I need to do a browser refresh to see if they ran, because the refresh feature is broken.

Has anyone had luck using this service? I suspect that I broke my dashboard when my first Canary died immediately.

This issue appears to be a console bug affecting your ability to view CloudWatch Synthetics canaries. The error message "t is not iterable" suggests there might be a problem with how the CloudWatch console is loading or processing your canary data.

Here are some troubleshooting steps you can try:

1. Clear your browser cache and cookies, or try using a different web browser to access the CloudWatch console.

2. Check your network connectivity, as firewall settings, VPN configurations, or general internet connectivity problems could be preventing the console from loading properly.

3. Verify that your IAM user or role has the necessary permissions to access and view the canaries.

4. Ensure you're in the correct AWS region where your canaries are deployed.

5. As an alternative to using the console while troubleshooting this issue, you can use the AWS CLI with the describe-canaries command to view your canary information. This would allow you to continue monitoring your canaries while the console issue is being resolved.

6. Check the AWS Service Health Dashboard to see if there are any ongoing CloudWatch service issues in your region.

If these steps don't resolve the issue, you may need to contact AWS Support for further assistance, as this appears to be a specific console rendering issue rather than a problem with your canaries themselves.
Sources
I have a bug in CLOUDWATCH | AWS re:Post
Limiting a user to viewing specific canaries - Amazon CloudWatch