I think for that we need to ensure that the s3 deletion process completes before sending the api response we can achieve it by modifying the delete project function to wait for the asynchronous deleteFilesFroms3 function to finish executing , for that we can use promises or asynchronous/await @lindapaiste what are your views on this , if this approach is correct , I would like to work on this issue

Can anyone please check where I am making a mistake in the AWS setup?
I have described my error in this thread: #2984

@lindapaiste what is your say on this ??

##Problem
The warning "Promise returned from deleteObjectsFromS3 is ignored" indicates that the deleteObjectsFromS3 function is returning a promise, but its resolution is not being handled properly. This warning suggests that there might be potential issues with the asynchronous operation not being properly managed, which could lead to unexpected behavior or resource leaks.

##Action to fix
To address this warning, you need to ensure that you handle the promise returned by deleteObjectsFromS3 appropriately. This typically involves using either async/await or .then() to handle the promise resolution and execution flow.

To fix the warning "Promise returned from deleteObjectsFromS3 is ignored," you can take the following actions:

1.Handle the Promise: Ensure that the Promise returned by deleteObjectsFromS3 is properly handled to avoid potential issues with asynchronous operations. We can use async/await or .then() to handle the Promise resolution and execution flow.
2.Using async/await

@lindapaiste I would love to fix this issue, please assign this to me.

@lindapaiste @raclim I think on the latest develop, we are already handling the promises returned from deleteFilesFromS3 using async/await. IMO async/await is much cleaner and modern way to handle promises instead of .then() and .catch(). I have just added more robust way to handle error in the catch block here