> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Catalog refresh now waits and fails the run on a failed step

> paradime catalog refresh now waits for every step, shows progress in the run log, and fails the Bolt run when a step fails. Add --no-wait for the old behavior.

*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](https://mintcdn.com/paradime-docs/7a3lHaRfdtArooSd/images/bolt-catalog-refresh-run-log.jpg?fit=max\&auto=format\&n=7a3lHaRfdtArooSd\&q=85\&s=b335bb08a7dba0c2e0259f81a3022088)

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.

> [!NOTE]
>
> 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](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-refresh-catalog.md#change-how-the-command-waits). 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](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-refresh-catalog.md#how-the-command-waits) and [Refresh the catalog](https://docs.paradime.io/developers/paradime-cli/catalog-cli.md#refresh-the-catalog). Shipped in Paradime v6.26.3.


## Related topics

- [Refresh Paradime Catalog](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-refresh-catalog.md)
- [Catalog CLI](https://docs.paradime.io/developers/paradime-cli/catalog-cli.md)
- [Run several jobs when a pull request merges](https://docs.paradime.io/guides/orchestrate-data-pipelines/run-several-jobs-on-merge.md)
- [Refresh your development catalog from the Code IDE](https://docs.paradime.io/changelog/2026-10-20/catalog-refresh.md)
- [Changelog](https://docs.paradime.io/changelog/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.