Can I alert on a value dropping below a line as well as above it?

Yes, Less than and Greater than both apply to A value, pick whichever direction matters for the number you're watching.

What's the difference between Equals and the other conditions?

Equals fires when the value matches exactly, useful for a status code or flag. Greater than and Less than are for a numeric line you don't want crossed in one direction.

Can I watch more than one column at once?

One value per watch. For several thresholds on the same query, save a separate watch per column, each with its own condition and destinations.

Does Increased by or Decreased by work with A value too?

Yes, if you want to alert on a relative jump since the last check rather than an absolute line, Increased by and Decreased by are available for A value as well as Row count.

Which tier includes threshold watches?

QueryFlow Pipelines. Studio includes the Scheduler with email and local-file destinations, not Watch This.

Alert When a Value Crosses a Threshold

Before you start

A query that returns the single value you want to track, and QueryFlow Pipelines.

Step by step

Run the query that returns the value you care about, then click Watch this.
Choose A value as what to watch, then pick the Column.
Choose a Condition: Greater than, Less than, or Equals.
Enter the threshold value the condition compares against.
Set Check every, choose Destinations, and Save.

A worked example: inventory dropping too low

On a Redshift-backed retail warehouse, watch a query like:

SELECT sku, quantity_available
FROM inventory.stock
WHERE sku = 'SKU-10432';

Choose A value, pick quantity_available, set the Condition to Less than 10, Check every 4h. Cross that line and the destinations you picked hear about it, instead of finding out when someone tries to order the item and can't.

A second worked example: a status flag with Equals

For a job-tracking table where a stuck run is marked with a specific status code, watch a query returning that status column and set the Condition to Equals with the stuck value. This catches a specific known-bad state directly, rather than trying to express it as a numeric threshold.

Check it worked

Run preview shows the current value against the threshold before you save. Use Check now afterward to confirm a real check fires and, if testing a Slack or Teams destination, that the message actually lands.

Troubleshooting

If you see	Fix
No alert even though the value clearly crossed the line	Double-check Greater than vs. Less than, it's easy to pick the wrong direction for the threshold you meant.
Constant alerts	The value may hover right around the threshold. Move the line, or switch to Increased by/Decreased by if what matters is the change, not the absolute number.
The Column list doesn't show the value you want	Confirm the underlying query actually returns that column by name; A value watches a named column in the result, not a computed value outside the query.

Threshold vs. row count

Threshold watches are for a specific number inside a result. If what matters is how many rows came back rather than a value inside them, see row count alerts instead.

Picking a sensible threshold

A line set too tight fires constantly and gets ignored; one set too loose misses the problem until it's already serious. Start with a number a bit beyond your normal range based on what you already know the value tends to do, then tighten it after a week or two of watching actual alerts against what really happened.

A third worked example: Databricks Unity Catalog usage

On a Databricks table tracking daily active users by catalog, watch a query returning that count with Condition Less than a floor you'd expect on a normal weekday. A sudden drop, from a broken upstream job or an authentication issue blocking a whole team, surfaces the same day instead of at the next manual review.

Alert when a number crosses a line.