The following lists error messages you may encounter while exporting data via CSV or API from Braze.
If you are using your own S3 bucket, this could happen because:
- The expected object is no longer in the S3 bucket; check with your engineers.
- The configured S3 credentials within the Braze dashboard do not have the correct permissions; confirm the proper credentials with your team.
If you are using Braze’s S3 bucket, this could happen because:
- The object is no longer there. This could occur if you clicked on a link for an export that ran 4+ hours ago. If this is the case, re-run your export.
- You clicked on the download link right away, before the S3 was ready to serve the object. Wait a few minutes and try again. Larger reports will generally take longer.
- The export is too big, so our server ran out of memory trying to create this zip file. We’ll automatically email the user attempting this export if this occurs. If you consistently run into this issue, we recommend that you use your own S3 buckets in the future.
This will happen if the email was sent 4+ hours ago. Re-run the export and download it within 4 hours. This could also be caused by Braze no longer having access to the S3 bucket you are downloading the data to. Make sure you’ve updated your S3 credentials using these steps.
“Looks like the file doesn’t exist anymore, please check to make sure nothing is deleting objects from your bucket”
There may be a slight lag between when Braze’s email with the export gets sent, and when S3 is actually ready to serve the object. If you see this error, wait a few minutes before trying again.