Skip to content

Commit

Permalink
[EWSv2] Updated troubleshooting docs with new skip_unparsable_emails …
Browse files Browse the repository at this point in the history
…integration parameter (#1649)

* Add EWSv2 skip_unparsable_emails parameter docs

* Add new line

* Revert change to origin

* Return only new docs changes
  • Loading branch information
samuelFain authored Nov 6, 2024
1 parent b9afcaa commit c9b2a6c
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions content-repo/extra-docs/articles/EWS_V2_Troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,12 @@ The following are examples of error messages that may occur even if the instance
5. If the error still occurs, contact Cortex XSOAR customer support.


## Fetching Incidents crash due to unparsable emails
If you find that your fetch incidents command is unable to parse a specific invalid email due to various parsing issues, you can follow these steps:

1. In the instance configuration, navigate to the *Collect* section and click on *Advanced Settings*.
2. Check the box labeled *Skip unparsable emails during fetch incidents*.



By enabling this option, the integration can catch and skip unparsable emails without causing the fetch incidents command to crash.
When this parameter is active, a message will appear in the "Fetch History" panel of the instance whenever an unparsable email is recognized and skipped.
This allows customers to be informed that a specific email was skipped and gives them the opportunity to open a support ticket if necessary.

0 comments on commit c9b2a6c

Please sign in to comment.