Some services like start-result-path are executing running (synchronously) propagation which is never supposed to be long. But if there is propagation scheduled by another service (for instance update item children) and this propagation is not done yet, the small-propagation service should not try to run the large one and possibly timeout.
On 28/03 we saw that the start-result service was blocked by ongoing propagation.
Could propagation have a parameter to just run a subset of the propagation?
Motivations
Some services like
start-result-pathare executing running (synchronously) propagation which is never supposed to be long. But if there is propagation scheduled by another service (for instance update item children) and this propagation is not done yet, the small-propagation service should not try to run the large one and possibly timeout.On 28/03 we saw that the
start-resultservice was blocked by ongoing propagation.Could propagation have a parameter to just run a subset of the propagation?
Subtasks