Skip to content
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

[BUG] docData Must Not Be Null Error in Findings Page #718

Closed
jowg-amazon opened this issue Nov 9, 2023 · 1 comment
Closed

[BUG] docData Must Not Be Null Error in Findings Page #718

jowg-amazon opened this issue Nov 9, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@jowg-amazon
Copy link
Collaborator

What is the bug?
If a detector generates a finding based on a document and its ID but then the document gets deleted, there is a docData must not be null error in the findings page and none of the findings appear.

How can one reproduce the bug?

  1. Create a detector with a rule
  2. Insert a document that generates a finding
  3. Delete the document
  4. Check the findings page

What is your host/environment?

  • OS: 2.9
@riysaxen-amzn
Copy link
Collaborator

closing in favor of 1325

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants