Hey @athavichith,
Before chasing a "recent vs old" theory, look again at the screenshot you posted: ADOREQ0001218 shows Insert Count 0, Update Count 0, and Failed Count 1,838 against a Total count of 1,838. That is not a partial skip of the older stories, that is every single work item in that request failing. So the actual question isn't why old items get filtered out, it's why that whole batch is erroring.
A few things worth checking before assuming it's a recency filter:
- Import Request Pages: open one of the IRQP records under that request (IRQP0001388 etc.) and see if there's an actual error message logged against the failed rows, not just the count.
- Correlation records: if any of these older stories were previously imported, deleted, or re-pointed to a different project, a leftover correlation entry on the Azure DevOps integration side can block re-insert of that same work item ID.
- Field mapping: check whether the older items carry State, Area Path, or Iteration Path values that have since been renamed or retired in Azure DevOps, that will fail validation on insert even though the field mapping itself looks fine.
- sys_log: filter around the Completed timestamp on the import request to catch the underlying exception for the failed rows.
If the mapping and logs come back clean, the fix that's worked for others stuck in this exact spot is deregistering the Azure DevOps connection and re-registering it, that clears the correlation records and forces a clean full re-import instead of a partial one.
Share the error text from one of those failed rows and I can narrow it down further.
Thank you,
Vikram Karety
Octigo Solutions INC
