Catch connector errors but do not interrupt the case creation flow#244188
Merged
janmonschke merged 2 commits intoelastic:mainfrom Nov 25, 2025
Merged
Conversation
janmonschke
added
release_note:fix
v9.0.0
backport:version
Contributor
|
Pinging @elastic/kibana-cases (Team:Cases) |
elastic-vault-github-plugin-prod
bot
requested a review
from a team
as a code owner
christineweng
approved these changes
Nov 25, 2025
delanni
approved these changes
Nov 25, 2025
Contributor
|
Starting backport for target branches: 9.0, 9.1, 9.2 |
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
|
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 25, 2025
…lastic#244188) ## Summary Addresses: elastic#243852 During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push. Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure. (cherry picked from commit 73b31bd)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 25, 2025
…lastic#244188) ## Summary Addresses: elastic#243852 During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push. Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure. (cherry picked from commit 73b31bd)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 25, 2025
…lastic#244188) ## Summary Addresses: elastic#243852 During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push. Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure. (cherry picked from commit 73b31bd)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
seanrathier
pushed a commit
to seanrathier/kibana
that referenced
this pull request
Nov 25, 2025
…lastic#244188) ## Summary Addresses: elastic#243852 During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push. Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure.
kibanamachine
added a commit
that referenced
this pull request
Nov 25, 2025
…low (#244188) (#244227) # Backport This will backport the following commits from `main` to `9.2`: - [Catch connector errors but do not interrupt the case creation flow (#244188)](#244188) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-11-25T17:40:59Z","message":"Catch connector errors but do not interrupt the case creation flow (#244188)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/243852\n\nDuring case creation, when the case connector failed to push, the case\ncreation form would get stuck in a loading state. To the user that\nlooked like the case had not been created and they'd lost their work.\nHowever, the case had been created but only the connector failed to\npush.\n\nSince the case connector issues can be resolved from the case page, we\ncan redirect users to the case page even when the connector fails to\npush. On top, a message is show to the user with details about the\nconnector failure.","sha":"73b31bd7d06db898ae31ce786297edb131b7d0ca","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:version","v9.1.0","Team:Cases","v9.2.0","v9.3.0"],"title":"Catch connector errors but do not interrupt the case creation flow","number":244188,"url":"https://github.com/elastic/kibana/pull/244188","mergeCommit":{"message":"Catch connector errors but do not interrupt the case creation flow (#244188)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/243852\n\nDuring case creation, when the case connector failed to push, the case\ncreation form would get stuck in a loading state. To the user that\nlooked like the case had not been created and they'd lost their work.\nHowever, the case had been created but only the connector failed to\npush.\n\nSince the case connector issues can be resolved from the case page, we\ncan redirect users to the case page even when the connector fails to\npush. On top, a message is show to the user with details about the\nconnector failure.","sha":"73b31bd7d06db898ae31ce786297edb131b7d0ca"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1","9.2"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/244188","number":244188,"mergeCommit":{"message":"Catch connector errors but do not interrupt the case creation flow (#244188)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/243852\n\nDuring case creation, when the case connector failed to push, the case\ncreation form would get stuck in a loading state. To the user that\nlooked like the case had not been created and they'd lost their work.\nHowever, the case had been created but only the connector failed to\npush.\n\nSince the case connector issues can be resolved from the case page, we\ncan redirect users to the case page even when the connector fails to\npush. On top, a message is show to the user with details about the\nconnector failure.","sha":"73b31bd7d06db898ae31ce786297edb131b7d0ca"}}]}] BACKPORT--> Co-authored-by: Jan Monschke <jan.monschke@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Nov 25, 2025
…low (#244188) (#244226) # Backport This will backport the following commits from `main` to `9.1`: - [Catch connector errors but do not interrupt the case creation flow (#244188)](#244188) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-11-25T17:40:59Z","message":"Catch connector errors but do not interrupt the case creation flow (#244188)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/243852\n\nDuring case creation, when the case connector failed to push, the case\ncreation form would get stuck in a loading state. To the user that\nlooked like the case had not been created and they'd lost their work.\nHowever, the case had been created but only the connector failed to\npush.\n\nSince the case connector issues can be resolved from the case page, we\ncan redirect users to the case page even when the connector fails to\npush. On top, a message is show to the user with details about the\nconnector failure.","sha":"73b31bd7d06db898ae31ce786297edb131b7d0ca","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:version","v9.1.0","Team:Cases","v9.2.0","v9.3.0"],"title":"Catch connector errors but do not interrupt the case creation flow","number":244188,"url":"https://github.com/elastic/kibana/pull/244188","mergeCommit":{"message":"Catch connector errors but do not interrupt the case creation flow (#244188)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/243852\n\nDuring case creation, when the case connector failed to push, the case\ncreation form would get stuck in a loading state. To the user that\nlooked like the case had not been created and they'd lost their work.\nHowever, the case had been created but only the connector failed to\npush.\n\nSince the case connector issues can be resolved from the case page, we\ncan redirect users to the case page even when the connector fails to\npush. On top, a message is show to the user with details about the\nconnector failure.","sha":"73b31bd7d06db898ae31ce786297edb131b7d0ca"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1","9.2"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/244188","number":244188,"mergeCommit":{"message":"Catch connector errors but do not interrupt the case creation flow (#244188)\n\n## Summary\n\nAddresses: https://github.com/elastic/kibana/issues/243852\n\nDuring case creation, when the case connector failed to push, the case\ncreation form would get stuck in a loading state. To the user that\nlooked like the case had not been created and they'd lost their work.\nHowever, the case had been created but only the connector failed to\npush.\n\nSince the case connector issues can be resolved from the case page, we\ncan redirect users to the case page even when the connector fails to\npush. On top, a message is show to the user with details about the\nconnector failure.","sha":"73b31bd7d06db898ae31ce786297edb131b7d0ca"}}]}] BACKPORT--> --------- Co-authored-by: Jan Monschke <jan.monschke@elastic.co>
eokoneyo
pushed a commit
to eokoneyo/kibana
that referenced
this pull request
Dec 2, 2025
…lastic#244188) ## Summary Addresses: elastic#243852 During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push. Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure.
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
…lastic#244188) ## Summary Addresses: elastic#243852 During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push. Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses: #243852
During case creation, when the case connector failed to push, the case creation form would get stuck in a loading state. To the user that looked like the case had not been created and they'd lost their work. However, the case had been created but only the connector failed to push.
Since the case connector issues can be resolved from the case page, we can redirect users to the case page even when the connector fails to push. On top, a message is show to the user with details about the connector failure.