Maybe play with additional triggers and documents?
Let's call your original documet A.
Create a dummy document C whose reload always succeeds (by doing nothing really in the load script.
Foir document C, define a task with a trigger that fires when your original document A fails.
Add a trigger to your document A that fires whenever the dummy document C succesfully completes a reload (in other words, always)
Add a trigger to the next document B that fires whenever document A does a succesful reload.
I never tried this (and I don't have a publisher on this machine). QMS may intercept circular task chains, like QV Desktop does with circular references.
And above all, I think this is a setup that cannot be decently shown in the QMC Task Status overview.
Maybe play with additional triggers and documents?
Let's call your original documet A.
Create a dummy document C whose reload always succeeds (by doing nothing really in the load script.
Foir document C, define a task with a trigger that fires when your original document A fails.
Add a trigger to your document A that fires whenever the dummy document C succesfully completes a reload (in other words, always)
Add a trigger to the next document B that fires whenever document A does a succesful reload.
I never tried this (and I don't have a publisher on this machine). QMS may intercept circular task chains, like QV Desktop does with circular references.
And above all, I think this is a setup that cannot be decently shown in the QMC Task Status overview.
