From bae49125942d5e6f50d4e0c08087cb9e44ff4f06 Mon Sep 17 00:00:00 2001 From: Rachel Feinberg Date: Tue, 7 May 2024 14:46:31 -0700 Subject: [PATCH 1/4] BD-3081 Update export troubleshooting --- .../export_braze_data/export_troubleshooting.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md index e66556da0e7..57cc8a38249 100644 --- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md +++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md @@ -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. @@ -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 appostrophe to a field in the CSV output 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`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/) endpoint. \ No newline at end of file From 729f1e518e03b7a87576098d3ced19d1156ab7a3 Mon Sep 17 00:00:00 2001 From: Rachel Feinberg <135255868+rachel-feinberg@users.noreply.github.com> Date: Tue, 7 May 2024 14:47:45 -0700 Subject: [PATCH 2/4] Update _docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md --- .../export_braze_data/export_troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md index 57cc8a38249..3d9ca628423 100644 --- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md +++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md @@ -35,7 +35,7 @@ There may be a slight lag between when Braze's email with the export gets sent, ### Apostrophes added to fields -Braze will automatically prepend an appostrophe to a field in the CSV output if the field begins with any of the following characters: +Braze will automatically prepend an appostrophe to a field in the CSV export if the field begins with any of the following characters: - - - = From fa924d75755a4fd924176eae9b7b9d7327dcb176 Mon Sep 17 00:00:00 2001 From: Rachel Feinberg <135255868+rachel-feinberg@users.noreply.github.com> Date: Tue, 7 May 2024 15:05:15 -0700 Subject: [PATCH 3/4] Update _docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md --- .../export_braze_data/export_troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md index 3d9ca628423..1660383827b 100644 --- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md +++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md @@ -35,7 +35,7 @@ There may be a slight lag between when Braze's email with the export gets sent, ### Apostrophes added to fields -Braze will automatically prepend an appostrophe to a field in the CSV export if the field begins with any of the following characters: +Braze will automatically prepend an apostrophe to a field in the CSV export if the field begins with any of the following characters: - - - = From bad12c041defd3895639b3b8c1a401287531957f Mon Sep 17 00:00:00 2001 From: Lydia Xie <87040416+lydia-xie@users.noreply.github.com> Date: Tue, 7 May 2024 15:48:09 -0700 Subject: [PATCH 4/4] Apply suggestions from code review --- .../export_braze_data/export_troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md index 1660383827b..6dfa94bc861 100644 --- a/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md +++ b/_docs/_user_guide/data_and_analytics/export_braze_data/export_troubleshooting.md @@ -42,4 +42,4 @@ Braze will automatically prepend an apostrophe to a field in the CSV export if t - + - @ -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`]({{site.baseurl}}/api/endpoints/export/user_data/post_users_segment/) endpoint. \ No newline at end of file +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/). \ No newline at end of file