We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 10 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
This would work for our use case. Thanks!
My initial thought is that we could capture a "refreshed on" date in PIM as we process the product records and add an option to skip any products that were already refreshed within the lookback period. Something like this might work and not be too difficult but I need to vet it with the team. This isn't something that we're likely to do in the near term but certainly a good enhancement when we take a look at the refresh job.
Just to clarify, its only the Refresh Published Products that would probably need this feature.
I figured it would be fairly complex. I'm sure you have better ideas, but maybe an optional start/end number or something like that? Assuming it always pulls in the same order (probably date published?)
PS - Sorry for all the typos there, I realized I had a lot rereading it.
The refresh job is trickier since it uses a lookback period to determine what data to pull to commerce. Since the publish job is updating products from approved to published as it runs, if it needs to be restarted it will only have a subset of products to publish. I have some ideas for parameters to the refresh job that could make it run in a more similar fashion and this is something we will consider in the future.