[Bug]: Azure Blog Storage Connector: Optimized sync facility no longer prevents documents that were previously ingested from being re-ingested

[mpawlow]

OpenRAG Version

0.6.2

Deployment Method

Local development (make dev)

Operating System

Ubuntu 24.04.4 LTS

Python Version

Python 3.13.14

Affected Area

Connectors (Google Drive, OneDrive, SharePoint)

Bug Description

• Optimized sync facility no longer prevents documents that were previously ingested from being re-ingested

Steps to Reproduce

• Go to Settings page
• Setup Azure Blob Storage connector.
• Click Add Knowledge button to go to the Add from Azure Storage pane
• Select container and click Ingest 1 Bucket
• Go to Knowledge page to ensure all files are successfully ingested
• Click Add Knowledge button to go to the Add from Azure Storage pane
• Select container and click Ingest 1 Bucket
  • BUG: All documents that are were previously ingested appear to be ingested again
    • i.e. Optimized sync facility no longer prevents previously ingested files from being re-ingested
  • BUG: Ingestion appears to be instantaneous; but, the state listed in the table for each document is stuck in Processing... and never transitions to Active - until you manually refresh the page

Expected Behavior

• Optimized sync facility prevents previously ingested files from being re-ingested
• Toaster to be shown indicating file ingestion was skipped because no out-of-date files were detected

Actual Behavior

• Optimized sync facility no longer prevents documents that were previously ingested from being re-ingested
• This is a regression

Relevant Logs

N/A

Screenshots

Additional Context

• For Azure Blog Storage connector setup instructions, see offline PDF file (OpenRAG - Azure Blob Storage Connector - Manual Testing Instructions.pdf)

Checklist

• I have searched existing issues to ensure this bug hasn't been reported before.
• I have provided all the requested information.

[mpawlow]

• ⚠️ Possibly related issue: [Bug]: Azure Blog Storage Connector: "Ingested" status badge no longer shown in "Browse Files" dialog for documents already ingested #2084

[mpawlow]

• Root Cause Analysis - Part 1
  • See: [Bug]: Azure Blog Storage Connector: "Ingested" status badge no longer shown in "Browse Files" dialog for documents already ingested #2084 (comment)
• Root Cause Analysis - Part 2
  • See: [Bug]: Azure Blog Storage Connector: "Ingested" status badge no longer shown in "Browse Files" dialog for documents already ingested #2084 (comment)

Resolving as a Duplicate of #2084