On-demand per-item retries are not foreseen any time soon. And tbh such an option might not be technically benefitial, given that SharePoint change tokens are provided per list (or per web, I don't exactly remember it, but it's a higher level than an item withing site - that's for sure). With the current default retries, VB365 already performs multiple attempts to resolve issues that occurred during the previous session run, and in addition to that there're 'hidden' retries for such items. An error/warning is thrown if all these attempt were unsuccessful, which also means that a retry initiated manually will complete with a similar outcome.
For longer running SharePoint jobs that we interrupted, we already added a mechanism in v8 to 'remember' which items have been processed before interruption, so that the next attempt skipped those and only start with remaining unprocessed items to speed things up.
For longer running SharePoint jobs that we interrupted, we already added a mechanism in v8 to 'remember' which items have been processed before interruption, so that the next attempt skipped those and only start with remaining unprocessed items to speed things up.
Statistics: Posted by Polina — Aug 22, 2025 12:34 pm







