Reactiv-Redeploy does not work properly: Steps:1. Headend node is out of sync2. Provision a policy with async commit queue  Provision failed as expect3. Do a sync-to to make headend not in sync4. Do "Reactive-Redeploy"  The provisioned policy is still in failed stateXRV9K 7.3.2.33I is used
 Hi Crystal,Please following the steps from wiki linked to resolve the issue.Sync-to and reactive-redeploy is not a right command in this case.Thanks,LinhBy reading the link, I am not sure for this scenario what would be the right command to use except for redeploy? We would like to know in what scenario can reactive-redeploy and redeploy-reconcile can be used?Read the link one more time and found there is flow for "Redeploy reconcile" under "Persistent Create Failure Recovery Flow". Need clarification on the followings:1. For this flow, one of the steps says "Sync from on device".   Is it to do a Sync from device action? copy the device config to NSO?2. I still do not see a flow for "Reactive Redeploy".  Can you share the flow for this action?Thanks.All the flows outlined are with respect to NSO being the source of the actions (ie NSO sync-from device)I**don't believe we have a flow outlined for reactive-re-deploy specifically. For the most part on how they differ, is that reactive-re-deploy is shallow and asynchronous by default. You can think of `reactive-re-deploy = re-deploy shallow` except `re-deploy shallow` is synchronous. There are some cases where reactive-re-deploy maybe helpful, but currently nothing comes to mind specifically for T-SDN. For now, you should just follow the wiki on the error flows that Linh forwarded and if any of the flows do not help then feel free to reach out again and we can go over steps to resolve the issue.Had webex with submitter and explained the difference