Skip to content

Commit

Permalink
Merge pull request #7320 from braze-inc/bd-3081
Browse files Browse the repository at this point in the history
BD-3081 Update export troubleshooting
  • Loading branch information
lydia-xie authored May 7, 2024
2 parents 90e271d + bad12c0 commit d2eae9d
Showing 1 changed file with 13 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ description: "This reference article covers some common troubleshooting scenario
## Common errors

#### 'AccessDenied'
### 'AccessDenied'

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.
Expand All @@ -24,12 +24,22 @@ If you are using a **Braze S3 bucket**, this could happen because:
- 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.

#### 'ExpiredToken'
### 'ExpiredToken'

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"
### "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.

### Apostrophes added to fields

Braze will automatically prepend an apostrophe to a field in the CSV export if the field begins with any of the following characters:

- -
- =
- +
- @

For example, the field "-1943" will be exported as "'-1943". This does not apply to JSON exports, such as those returned by the [`/users/export/segment` endpoint]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/).

0 comments on commit d2eae9d

Please sign in to comment.