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

[ImportDocument] Connector's looping with a specific .pdf #3341

Open
NiQuintin opened this issue Jan 28, 2025 · 2 comments
Open

[ImportDocument] Connector's looping with a specific .pdf #3341

NiQuintin opened this issue Jan 28, 2025 · 2 comments
Labels
bug use for describing something not working as expected needs more info Intel needed about the use case

Comments

@NiQuintin
Copy link

Description

The connector is looping while trying to ingest a specific .pdf attachement (added here).

Environment

OpenCTI 6.4.9

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Uploading the .pdf either in a container/entity or in Data>Import.

Expected Output

The .pdf is processed and a workbench is created.

Actual Output

The connector is looping.

Additional information

Visible in testing instance. The .pdf is here 👇.

Screenshots (optional)

Image

infostealer.pdf

@NiQuintin NiQuintin added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 28, 2025
@romain-filigran
Copy link
Member

I'm unable to reproduce the problem. The file is correctly processed but the process takes time.
Can you try again with the latest version?

@romain-filigran romain-filigran added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team labels Feb 3, 2025
@NiQuintin
Copy link
Author

Still have the same issue, this time with an error in the end ('name': 'DATABASE_ERROR', 'error_message': 'Id loading expect only one response' I guess it's not related to the .pdf):

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected needs more info Intel needed about the use case
Projects
None yet
Development

No branches or pull requests

2 participants