Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processing subscription iterates events descending to its Id's #4817

Closed
tw17 opened this issue Aug 16, 2018 · 2 comments

Comments

@tw17
Copy link

commented Aug 16, 2018

When we process subscriptions we process them in decending order to their Id's this means that if the two events "Deployment Started" and "Deployment Finished" are processed in the same batch, they will be processed in the wrong order "Deployment Finished" and then "Deployment Started"

@tw17 tw17 added the area/execution label Aug 16, 2018
@tothegills tothegills self-assigned this Nov 9, 2018
@tothegills tothegills closed this Nov 14, 2018
@octoreleasebot octoreleasebot added this to the 2018.9.10 milestone Nov 14, 2018
@octoreleasebot

This comment has been minimized.

Copy link

commented Nov 14, 2018

Release Note: Subscription emails now display events in ascending order by the time the event occurred

@lock

This comment has been minimized.

Copy link

commented Feb 12, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
4 participants
You can’t perform that action at this time.