Skip to main content
November 19, 2026
A Bolt run with four steps, each Success, and the Logs of the paradime catalog refresh step: dbt docs generate, DataHub push, Read dbt artifacts, and Catalog build each start, report progress, and finish, ending with done in 3m41s, 4 of 4 steps succeeded
Until now, paradime catalog refresh started a Catalog refresh and finished at once, so a Bolt run passed even when the refresh failed later. The command now waits until every step of the refresh ends, and shows the progress of each step in the run log.
  • A failed step fails the run. The command prints the end of the failed stepโ€™s output and exits with an error.
  • Integration pushes count. The refresh ends only when the DataHub and Altimate pushes end, and a failed push fails the command. Add --allow-integration-failures to let the command pass when only a push fails.
  • Two hours at most. After 2 hours, the command fails and the refresh continues. Change the limit with --timeout.
  • One refresh at a time. If a refresh is already running, the command follows that refresh instead of starting another one.
If a schedule runs Refresh Paradime Catalog, its runs now last until the refresh ends, and they fail when the refresh fails. To keep the old behavior, set the command to paradime catalog refresh --no-wait in schedules as code. The Refresh Paradime Catalog command type in the app doesnโ€™t take flags.
The command works the same way in your terminal with the Paradime Python SDK 6.12.0 or later. See How the command waits and Refresh the catalog. Shipped in Paradime v6.26.3.