JFrog Connect
HomePricingDashboardRegister Now
Search…
JFrog Connect
OVERVIEW
Architecture
Getting Started
JFrog Platform
Register
Register a device
Registering devices at scale
Registering Yocto image
Create Update
Update Flow
Integrations
Upload Files
Deploy Files
Deploy Container
Git Repository
Artifacts
Release Bundle
Create Update Parameters
Rollback
Update Devices
Update Deployment
Applications
Deployment Best Practice
Device Registration & Deployment
Schedule Update
Deploy Update Parameters
Devices
Filter bar
Map / Location
Delete a device
Control Center
Remote control
Remote access
Remote commands
Monitor
Resources monitor
Processes monitor
Data monitor
Alerts
Overview
Webhook
Fetch
Fetch logs
Device security
Active
REST API
Overview
Device state
Bulk devices state
Get devices details
Change devices details
Data monitor
Deploy Update
Update Trigger
Tags
Apps
Environment
Environment variables
Running Commands as User
SETTINGS
Account
User management
Notifications
Security
Troubleshooting
Device registration
Display issue - "0.0"
Micro update
Remote control
FAQ
GENERAL TERMS OF SERVICE
Frequent questions
Service-Level Agreement
Billing
Deprecated
Deprecated OTA updates tools
Deprecated REST API endpoints
Non-Linux Agent
Powered By GitBook
Rollback
JFrog Connect Agent supervises your device and wraps your updates in a Rollback engine, which is able to revert any update to the previous state, allowing the device's software to be 100% reliable.

On Fail Configurations

All Action Blocks have On Fail configurations in addition to the Action configuration.
When an Action Block fails to run or raises an exception, the Action Blocks "On Fail" is triggered. The "On Fail" configuration contains the Continue Update Flow checkbox, the Run General Rollback checkbox, and in some Blocks a Do Action section.
After the "On Fail" finishes the Update exits.

Continue Update Flow

Default - unchecked. If checked, the Update will continue as if the Action Block succeeded. In the Deployment Output you will still see that the Action Block failed and the error that caused the failure. When checked, all other On Fail options are deselected.

Run General Rollback

Default - checked. If checked, the Update will trigger the General Rollback Block if the Action fails. * The General Rollback will run after the On Fail Actions of all blocks have finished.

Do Action - (Not all Actions)

Default - unchecked. This section defines an additional rollback action to preform when the action fails. You can choose one of two options - Whole Update Fails or This Action Fails Only. Whole Update Fails
*Requires Agent Version 6.0 or above.
The rollback action will run if any actions after the current action fail (including the current action).
This Actions Fails Only
The rollback action will run only if the current action failed.
​
Revert Files
Reverts all files/containers changed in the block, to their previous state. The rollback actions run in the same order as the Action Blocks.

General Rollback

We highly recommend adding General Rollback to each Update Flow. The General Rollback runs only if the update fails and the Action Block that failed had the Run General Rollback checked. The purpose of the General Rollback is to ensure that no matter what your application will always be able to return to a stable and running state.
Create Update - Previous
Create Update Parameters
Next - Update Devices
Update Deployment
Last modified 3mo ago
Copy link
Outline
On Fail Configurations
Continue Update Flow
Run General Rollback
Do Action - (Not all Actions)
General Rollback