🪄 RETRY by Rose — How-to
Make recoverable interruptions easier to handle. 🌹
Recorded status: Concept. Availability labels describe the project record; they do not promise a public release.
🚀 A practical workflow
- Open Retry by Rose when released
- Choose a failed or interrupted action
- Read the reason it stopped
- Retry only if the action is safe and eligible
- Review the new result
- Stop if a real approval or security gate remains
🧪 Try this
Retry a failed read-only status request after a temporary error.
🧯 If the result looks wrong
Stop. Keep the original. Compare the result with your request; don’t press retry and hope the goblins have learned manners. See Troubleshooting for Petal-specific checks.
Use these steps only if the matching controls exist in your build. A planned feature is not a hidden quest item.
🌹 Page art is decorative; it does not show the product UI.