Hi @Francois_Charlier Are you still running into this error? It would be helpful to see some screenshots. Is there anything different about the request compared to the other apps? (i.e different destination, different resource credentials, etc)
I checked on this internally as well, and the only known bug I can find related to this is that the S3 Query doesn't handle special characters in file paths properly. Definitely want to sort out why it isn't working in your instance though!
Also happy to take a look in office hours if you'd prefer