# Orchestration (in the sense.... Order of execution) of expectations in an expectations suite

**URL:** <https://discourse.greatexpectations.io/t/orchestration-in-the-sense-order-of-execution-of-expectations-in-an-expectations-suite/771>\
**Category:** Feedback\
**Created:** [May 27, 2021, 10:02am UTC](https://discourse.greatexpectations.io/t/orchestration-in-the-sense-order-of-execution-of-expectations-in-an-expectations-suite/771 "2021-05-27T10:02:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![patechoc](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@patechoc](https://discourse.greatexpectations.io/u/patechoc)\
**Post date:** [May 27, 2021, 10:02am UTC](https://discourse.greatexpectations.io/t/orchestration-in-the-sense-order-of-execution-of-expectations-in-an-expectations-suite/771/1 "2021-05-27T10:02:26Z")

</div>

Hi,

I know Great Expectations has no intent to replace tools like Dagster, AirFlow, … but as a use case, we would be interested in running the expectations of an expectations suite in a given order.

That way we could simply, NOT evaluate the other tests if expect\_table\_row\_count\_to\_be\_between(min\_value=1) fails. That is an obvious useful example for many most probably and we can think of more complex relations between the expectations.

Just let us know if this could be on the roadmap or most probably “never” 😉

Cheers  
Patrick

---

<div class="post-metadata">

**Author:** ![eugene.mandel](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/eugene.mandel/32/22_2.png) [@eugene.mandel](https://discourse.greatexpectations.io/u/eugene.mandel)\
**Post date:** [June 14, 2021, 3:27pm UTC](https://discourse.greatexpectations.io/t/orchestration-in-the-sense-order-of-execution-of-expectations-in-an-expectations-suite/771/2 "2021-06-14T15:27:53Z")

</div>

@patechoc This is a great point. Eventually, the code that evaluates a suite will be “smart” enough to figure out these dependencies.