Why does Chromium/ Synthetic show as failed, skipped, or rollback in Deployment Status when it is up to date?

HannahM — Wed, 11 Mar 2026 10:18:35 GMT

Summary

If your ActiveGate is fully up to date but the Deployment Status → ActiveGates → ActiveGate view shows that Chromium or the Synthetic module has a Last Update status of Failed, Skipped, or Rollback, the behavior is expected.
This happens when a previous update attempt had issues, and the component was later updated manually or outside the normal autoupdate process.

Chromium and Synthetic have separate update mechanisms, but the underlying reason is similar:
➡️ A past update failed or was skipped, and the status is not overwritten until the next successful automated update.

Chromium

Why does Chromium show as failed or skipped when it's up to date?

When viewing Deployment Status → ActiveGates → ActiveGate, you may see the Chromium Last Update status listed as Failed or Skipped despite Chromium being on the expected version

Answer

The Synthetic installer determines the Chromium Last Update status.

Here’s why the status may not show “OK”:

Previous Chromium autoupdate failed

If a Chromium autoupdate attempt fails, the Last Update status is set to Failed.
If Chromium is later manually updated, the version will be correct, but the status will remain Failed.

Chromium autoupdate is disabled

If the autoupdate option is turned off, Chromium updates are skipped by the installer.
The Last Update status remains Skipped.

How to reset the status

The Chromium Last Update status will return to OK only after a successful Chromium update performed by the Synthetic installer.

Synthetic module

Why does Synthetic show as failed, skipped, or rollback when it's up to date?

When viewing Deployment Status → ActiveGates → ActiveGate, the Synthetic module’s Last Update status may show Failed, Skipped, or Rollback, even though the module is up to date.

Answer

The Autoupdater sets the Last Update status for the Synthetic module.

Here’s what causes the unexpected status:

A previous update attempt failed

If the Synthetic module update failed earlier and you later:

uninstalled it
reinstalled it
…the Last Update status does not automatically change.

How to reset the status

The Synthetic Last Update field is refreshed only when the ActiveGate itself is next updated successfully.

What's Next

If the explanations above don't answer your question, please ask below or open a Q&A in the Synthetic forum.

article Why does Chromium/ Synthetic show as failed, skipped, or rollback in Deployment Status when it is up to date? in Troubleshooting

Why does Chromium/ Synthetic show as failed, skipped, or rollback in Deployment Status when it is up to date?

Summary

Chromium

Why does Chromium show as failed or skipped when it's up to date?

Answer

Previous Chromium autoupdate failed

Chromium autoupdate is disabled

How to reset the status

Synthetic module

Why does Synthetic show as failed, skipped, or rollback when it's up to date?

Answer

A previous update attempt failed

How to reset the status

What's Next

Related reading