Naming conventions are sometimes buggy in subfolders.

Thanks for the images. I've managed to replicate the same behavior you mentioned, and after a lot of testing, I was able to figure out how to avoid this, and more importantly, why this is happening.

Long story short, to prevent this from occurring in subfolders, on the File request page, click the 'Set naming conventions button' there:

Then, for the next window, remove the Sender's name option entirely so it looks like this.

The folder I chose is a subfolder of a page with the exact automation you created, and all files came out with the correct name.

Now, if you want to know why this was occurring, because file requests automatically add the sender's name in the default naming convention after the filename, this means that files would look like 'test1 Jay.png'.

After doing the tests, my belief is that Dropbox can only access the 'sender's name' once in total. So, when the automation tried to add a sender name, it couldn't access it, and left it blank.

The filename itself, which is then added by the automation 'correctly' would be the test1 Jay.png, which was generated by the original naming convention in the file request, hence the wrong order you were seeing (with sender name and filename in a different order on your end).

When you remove the sender's name from the original file request, the parent folder automation would be able to grab that variable, and then put it in the correct order.

Could you test this out and let me know if this helps?