- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes REVIVE, which monitors execution progress and phase boundaries, performs limited local action rollback upon detecting anomalies, and regenerates actions. To reduce repeated failures, the method incorporates Decoder Adaptation, which temporarily adjusts some action decoder parameters, and Failure-Guided Selection, which ranks candidate actions using the similarity and density of recorded failed actions. The authors evaluate overall performance on LIBERO, LIBERO-plus, and two real robot tasks with their OOD settings, and analyze the roles of different recovery components through ablations.
Critical strengths
The issue of stage failure propagation addressed by the paper is of practical significance. Local rollback can attempt to preserve previously completed task progress, while failure-guided action generation and selection target the specific problem of repeatedly executing similar failed actions. Experiments cover multiple VLA backbones, simulation perturbations, and real robots, and the reported results show that the overall approach has the potential to improve task completion rates. The authors also explicitly discuss limitations such as action replay being unable to restore complete physical states, and failure density not being equivalent to success probability.
Critical weaknesses
The critical ablation results in the main text and appendix are inconsistent. For the π0 model on LIBERO with configurations of the same name, Table 4 reports average success rates of 97.45% and 97.75% for Return + FGS and Return + DA respectively, while Table 8 reports corresponding values of 91.10% and 92.00%. However, the average results for the base model, Return, and complete REVIVE are consistent across both tables.
Questions for authors
Please explain why the results for π0's Return + FGS and Return + DA in Table 4 and Table 8 are different. Do they come from different implementations, checkpoints, evaluation samples, or experimental settings? If so, please clearly label the configurations and differences for each row, and indicate which set of results should serve as the primary basis for ablation; if this is a reporting error, please unify the tables, related main text conclusions, and cost statistics.
Response to Reviewer U8vV
We thank the reviewer for checking the tables closely; this was the most consequential issue in the review.
Q1: Why do Table 4 and Table 8 differ for π₀ Return + FGS and Return + DA?
This is a reporting error on our part, not a difference in implementation, checkpoint, evaluation samples, or experimental settings. The two rows in the main table were copied from an inconsistent intermediate result, while the appendix contains the final configuration. The reviewer's observation about which rows agree is exactly right: Baseline, Return, and complete REVIVE were transcribed correctly, and only these two were not.
Corrected π₀ ablation, now identical in both tables:
Following the reviewer's request to indicate which results should serve as the primary basis: the appendix configuration is the primary one, and we have unified the main table, the appendix table, the accompanying text, and the cost statistics around it. We have also re-derived the bold and underline markings from the corrected values, labeled the checkpoint, per-suite episode count, and controller protocol in both captions, and noted in the main caption that the Return-to-Start row uses a different evaluation budget (400 versus 2,000 episodes) — a detail that was previously only in a source comment.
As we noted in our response to Reviewer sirW, who raised the same discrepancy, the corrected numbers do not weaken the ablation: the complete method exceeds every single-component variant on every suite, with +5.9 pp average and +10.4 pp on the long-horizon suite over the strongest single component.