"AWS What's New?" doesn't work as before

And the latest tagged articles date back to 2-3 of July! Enter image description here

It sounds like you're experiencing an issue with filters not working as expected in an AWS service. Based on your description, there could be several reasons why your filters aren't returning results anymore:

1. Filter behavior may have changed from OR to AND logic - Previously, selecting multiple filters might have operated with OR logic (showing results matching any selected filter), but now it might be using AND logic (requiring all selected filters to match).

2. Case sensitivity might be affecting your results - AWS filters are often case-sensitive, so ensure your filter terms match the exact case of what you're searching for.

3. There could be a time delay in data processing - Some AWS services have delays between when data is generated and when it becomes available for filtering.

4. Filter syntax might have changed - The way filters are applied or the syntax required might have been updated.

To troubleshoot, you could try:

• Applying fewer filters at once to see if results appear
• Checking if there's a new way to explicitly set OR logic between filters
• Verifying that the data you're trying to filter actually exists within your selected time range
• Running a query without filters to confirm data is present

Without knowing which specific AWS service you're referring to (CloudWatch, Resource Explorer, etc.), it's difficult to provide more specific guidance on what might have changed in the filtering behavior.
Sources
AWS Cloudwatch filterquery not working as expected | AWS re:Post