# Striim Cloud4.1.0documentation

### QUIESCE

QUIESCE <namespace>.<application name> [CASCADE];
1. Pauses all sources.

2. Flushes out all data in process. This can result in partial batches of events, such as a 100-event window emitting a batch of only 20 events, or a five-minute window emitting a one-minute batch, which may result in functions such as COUNT and SUM returning anomalous results outside of the normal range. Pattern matching CQs may also return anomalous results.

3. After all data is flushed, records all information required for recovery, if it is enabled (see Recovering applications).

4. Stops the application. Its status will be QUIESCED.

If you specify the CASCADE option, any downstream applications that consume events from the specified application via persisted streams will also be quiesced.

### Note

If when you start an application for the first time it reads from a persisted stream that was previously quiesced, it will start reading the stream after the point at which it was most recently quiesced. Similarly, if an application was offline when an upstream application was quiesced, when it gets to the quiesce command in the persisted stream it will quiesce.

The primary uses for QUIESCE are to flush out remaining data at the end of a data set and to create a recovery checkpoint with no data in process prior to using ALTER on an application with recovery enabled (see ALTER and RECOMPILE).

Due to long-running open transactions, OracleReader may be unable to pause within 30 seconds, in which case the application and all its sources will resume as if the QUIESCE command had not been issued.

To support QUIESCE with OracleReader, see Creating the QUIESCEMARKER table for Oracle Reader.