- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper proposes RRI-VLA, a framework that combines online failure recovery with cross-episode self-improvement for vision-language-action models. During execution, a frozen multimodal reasoner generates structured feedback from action outcomes, while a Recovery Orchestrator determines when corrective actions are needed. After each episode, an offline verifier identifies successful recovery experiences, which are used to update a Recovery Critic without further training the action-generating VLA. Experiments on LIBERO-Plus and LIBERO-PRO demonstrate improved task success rates and recovery performance under distribution shifts.
Critical strengths
- The paper combines online failure recovery with cross-episode self-improvement, forming a complete self-improvement loop. In addition to recovering from failures in the current task, the framework can accumulate failure and recovery experience for future improvement.
- The framework does not require continuous updates to the VLA. After initialization, only the Recovery Critic is trained.
- The experimental improvements are relatively significant. RRI-VLA achieves 92.47% on LIBERO-Plus and 57.84% on LIBERO-PRO, improving over the online-only version by 3.12 and 5.64 percentage points, respectively.
Critical weaknesses
- Some important implementation details are still unclear. The paper describes what the verifier labels mean, but not exactly how they are computed. The initialization data and failure-to-instruction mapping also need more detail.
- The experiments are limited to simulation. Appendix C.8 provides useful cost measurements, but the absolute latency and full-system delay on physical robots remain unclear.
- Table 3 includes an external-reflection baseline, but comparisons with recovery methods such as ReCoVLA or AFI would better establish the contribution, with differences in supervision and sensing made clear.
Questions for authors
- What signals and rules produce the recovery-value and failure labels?
- What data are used for interface initialization, and how is the structured feedback constructed?
- How are failure classes mapped to corrective instructions? Please also clarify the absolute reflection latency and total execution overhead.