Hi @Lee_S, I am sorry you’re having trouble. From giving this a quick go on my own n8n instance I was unfortunately not able to reproduce this.
Can you confirm how exactly you have created the example documents on your S3 instance? Are you using actual folders or folder-like prefixes (see Understand prefixes and nested folders in Amazon S3 | AWS re:Post for the technical difference - iirc the AWS UI makes them look the same)?
Can you confirm the JSON data you’re sending to your S3 node? Thank you!
I’ve actually modified this automation several times since I posted so I can’t really dig into the diagnosis. Lets close this for now as a fluke and I’ll re-open if needed. I’m on a project where I’m doing a lot of S3 work so if it’s really a bug I’ll almost certainly encounter it again.