Skip to content

Update Reprocessing docs / Screenshot #9627

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
8 changes: 2 additions & 6 deletions docs/product/issues/reprocessing/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,9 @@ files](/platforms/native/data-management/debug-files/) only after they have been

<Include name="only-error-issues-note.mdx" />

After becoming an Early Adopter, you will find a new button when viewing an issue:
After becoming an Early Adopter, you will find a new action when viewing an issue:

!["Reprocess this issue" button next to Resolve, Archive, Share, Delete actions in issue details page](./img/reprocessing-btn.png)
!["Reprocess Event" action among advanced actions on issue details page](./img/reprocessing-action.png)

The dialog requires two answers:

Expand All @@ -40,10 +40,6 @@ Note that you can still get to the issue manually by searching for
The dialog to start reprocessing notes a few caveats that you
should be aware of and understand before you begin reprocessing.

- **Native only.** Reprocessing is only available for native events, and events
containing native frames. On issues that do not contain native events, the
button is hidden.

- **Data glitches.** During reprocessing you may observe temporary data
inconsistencies across the entire product. You may observe that an event belongs to
two issues at once, and appears in Discover queries twice.
Expand Down