Skip to content

Conversation

@hussein-awala
Copy link
Member

closes: #31795

I think we should stop executing the trigger once we find a message, and we should waiting for the next differing to continue processing the other messages.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

…esired format

Signed-off-by: Hussein Awala <hussein@awala.fr>
@hussein-awala
Copy link
Member Author

@dylanbstorey could you review this PR?

Copy link
Contributor

@dylanbstorey dylanbstorey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AwaitMessageTriggerFunctionSensor not firing all eligble messages

4 participants