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

Revert "[ResponseOps] Retry bulk update conflicts in task manager" #149038

Merged
merged 1 commit into from
Jan 17, 2023

Conversation

mikecote
Copy link
Contributor

Reverts #147808

@mikecote mikecote added Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 17, 2023
@mikecote mikecote self-assigned this Jan 17, 2023
@mikecote mikecote marked this pull request as ready for review January 17, 2023 13:39
@mikecote mikecote requested a review from a team as a code owner January 17, 2023 13:39
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@mikecote mikecote added release_note:skip Skip the PR/issue when compiling release notes v8.7.0 labels Jan 17, 2023
@mikecote mikecote enabled auto-merge (squash) January 17, 2023 13:45
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @mikecote

@mikecote mikecote merged commit a4cf50c into main Jan 17, 2023
@mikecote mikecote deleted the revert-147808-alerting/check-bulk-results branch January 17, 2023 15:18
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Jan 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Task Manager release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.7.0
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

5 participants