Skip to content

[9.1] Catch connector errors but do not interrupt the case creation flow (#244188)#244226

Merged
kibanamachine merged 3 commits intoelastic:9.1from
kibanamachine:backport/9.1/pr-244188
Nov 25, 2025
Merged

[9.1] Catch connector errors but do not interrupt the case creation flow (#244188)#244226
kibanamachine merged 3 commits intoelastic:9.1from
kibanamachine:backport/9.1/pr-244188

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…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 kibanamachine added the backport This PR is a backport of another PR label Nov 25, 2025
@kibanamachine kibanamachine enabled auto-merge (squash) November 25, 2025 17:50
@kibanamachine kibanamachine merged commit d807798 into elastic:9.1 Nov 25, 2025
12 checks passed
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
cases 1.4MB 1.4MB +16.0B

History

cc @janmonschke

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

Labels

backport This PR is a backport of another PR

3 participants