Prevent Sales Order Agent from skipping emails moved into monitored folders

[tomasevicst]

What & why

Stop advancing Earliest Sync At after email polling. Moved emails retain their original received timestamp, so advancing this value could permanently exclude them from later retrieval.

The configured Start Date remains the retrieval lower bound, while Graph excludes emails already categorized as processed. Added regression tests for empty and under-full polling.

Linked work

Fixes AB#648911

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

Risk & compatibility

Low risk. No schema, API, setup, or connector changes. Existing Start Date behavior during setup, reactivation, and mailbox changes remains unchanged. Previously processed emails continue to be excluded server-side by their Outlook category.

[alexei-dobriansky]

Good Sense Reviewer - Round 1

Recommendation: Accept with Suggestions

What this PR does

This change stops advancing the Sales Order Agent email retrieval lower bound after each folder poll. That lets a message still be found if it was received earlier but moved into the monitored folder after a previous empty poll. Processed messages are still excluded by the existing Outlook category filter, so the change relies on that category as the duplicate guard.

Problem-solution fit

Fit: Strong

The reported problem is a race between folder moves and a received-time polling watermark. Removing the runtime watermark update directly addresses that race, and the surrounding retrieval still filters by folder and excludes messages already marked as processed.

Suggestions

S1 (🟠 Moderate): Add folder polling regression coverage
The changed path removes the only runtime update of the retrieval lower bound, but this diff does not include a test for that behavior. Please add a test for an empty or under-limit folder poll, or explain why the connector mock cannot cover it.

Risk assessment and necessity

Risk: The regression surface is folder-based email polling in Sales Order Agent. The main risk is repeated scanning from the configured lower bound, but the folder filter, max-email limit, and processed category still bound normal processing and duplicate handling.

Necessity: The change is needed because moved messages keep their original received time. Without this change, a successful empty poll can permanently exclude an eligible message from later retrieval.

---

[AI-PR-REVIEW] version=1 promptVersion=4 system=github pr=11063 round=1 by=alexei-dobriansky at=2026-09-04T18:15:21.3645173Z lastSha=b4243ea664021c78f129280cf662a2328b7fc19c reviewKey=a2d7df95cdbc83488abc15b99b58305851d0451ad3f6613c32c9a7a9d9e997d2 suggestions=S1@1f0e1b8e

[Predrag Maricic (PredragMaricic)]

The change correctly preserves the configured Start Date as the retrieval lower bound, preventing emails moved into a monitored folder after receipt from being permanently excluded. Processed messages remain excluded server-side by category, and the change is narrowly scoped.