Troubleshooting FAQ

Start by checking whether:

• The file or related content was indexed successfully.
• The input file or image is clear enough.
• The relevant repositories are included in scope.
• Filters are narrowing the result set too much.
• The expected match actually exists in the indexed environment.

A file may appear missing if it was never indexed, failed during indexing, is outside the connected repositories, or is hidden by access rules or filter choices.

Indexing speed can vary based on file volume, file complexity, infrastructure, queue behavior, and the amount of extraction or processing required for each asset.

It helps to gather:

• The file or example search that failed.
• The expected result.
• The actual result.
• The repository or source involved.
• Approximate time of the issue.
• Any visible error messages or environment notes.

First confirm the file is present, accessible, and indexed correctly. If the file is available but the result quality is poor, the issue may be search-related. If the file never entered the searchable index correctly, the issue is likely earlier in the pipeline.

• Review Best practices for indexing and search quality guidance.
• Check Deployment if the issue may involve environment setup or infrastructure behavior.
• Use the API docs if the issue appears during an integration workflow.