mirror of
https://github.com/langgenius/dify.git
synced 2026-10-04 13:47:55 +08:00
A recovery_continue (Retry) re-runs the interrupted working handler, which re-invokes the state's privileged op -- publish (RELEASE) at build.publish/ fix.publish, a draft test run (TEST_AND_RUN) at the test/verify states. Before this, recovery_continue was classified as base EDIT, so a Retry re-ran the privileged op below its own authorization tier without re-checking. Make _app_access_for_action state-aware for recovery_continue so it enforces the same tier the state's normal action requires. recovery_restart only resets + re-enters the entry state, so it stays EDIT. Also: an interrupted working step now always surfaces the Retry/Start-over offer, overriding a stale drift recovery_class a user may have left set at an earlier waiting gate (drift recovery only applies at a waiting gate). Addresses the two findings from the final reconciliation review. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>