Skip to main content
Force flush gets changes to your destination faster for a short time without editing your flush rules. Use it when you need fresher data for the next couple of hours, such as while you check a fix or catch up after a busy period. After 2 hours, Artie puts your settings back.

​
What force flush changes

For 2 hours after you start it:
  • Flush interval: the pipeline’s flush interval is capped at 30 seconds. If it’s already 30 seconds or less, it doesn’t change.
  • Snowflake eco mode: off for the pipeline. See Snowflake eco mode.
  • Multi-step merge: off for every table that uses it. See Enable multi-step merge.
The row-count and byte-size flush conditions don’t change. Tables set to Run this table on its own deployment keep their own flush rules. Starting a force flush deploys the pipeline so the new settings take effect.
Flushing more often means more, smaller merges. On OLAP destinations like Snowflake, BigQuery, and Databricks, this can raise your compute costs while force flush is on. See Tuning flush rules.

​
What you’ll need

  • Edit access to the pipeline. View-only users don’t see Force flush.
  • A running pipeline. Paused pipelines don’t show Force flush.
  • No undeployed changes. Deploy or discard them first.
  • No deploy in progress. Wait for the current deploy to finish.

​
Force flush a pipeline

1

Open the pipeline

In the Artie dashboard, click the pipeline in your pipeline list.
2

Click Force flush

On the destination card, click Force flush.
3

Confirm

Review what changes for your destination, then click Force flush.
The destination card shows Force flush is on until followed by the end time. Force flush is hidden until the 2 hours are up.

​
When force flush ends

After 2 hours, Artie restores your previous flush interval, Snowflake eco mode, and multi-step merge settings, then deploys the pipeline. Artie only restores a setting that still has its force flush value. If you changed a setting to a new value during the 2 hours, your change stays. If the pipeline has undeployed changes when force flush ends, Artie saves the restored settings but doesn’t deploy them. The force flush settings stay live until your next deploy, which ships your changes and the restored settings together.

​
Advanced

Hover over or focus the button to see why:
  • Deploy this pipeline’s pending changes before force flushing. Force flush deploys the pipeline, which would also push your pending changes live. Deploy or discard them first.
  • This pipeline is deploying. Force flush once the deploy finishes. A deploy that’s already running would overwrite the force flush settings.
No. There’s no way to end force flush before the 2 hours are up. To change your flush settings sooner, edit them in the pipeline settings and deploy. Artie keeps the values you set when force flush ends.
No. Force flush is only available in the Artie dashboard.