Skip to content

Declarative Automation maximum evaluation per tick #24930

Answered by garethbrickman
liongkj asked this question in Q&A
Discussion options

You must be logged in to vote

The AutomationConditionSensorDefinition is going to target a set of assets and repeatedly evaluate all the AutomationConditions on all of those assets. So you would either need to change the number of assets being targeted, or change the AutomationConditions. There is no setting at the level of the AutomationConditionSensor for limiting/queuing the materializations themselves.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@liongkj
Comment options

@garethbrickman
Comment options

Answer selected by liongkj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
area: declarative-automation Related to Declarative Automation, AutomationConditions and Auto Materialization area: concurrency Related to controlling concurrent execution
2 participants