Skip to content

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

Closed
kibanamachine wants to merge 1 commit into
elastic:9.0from
kibanamachine:backport/9.0/pr-244188
Closed

[9.0] Catch connector errors but do not interrupt the case creation flow (#244188)#244225
kibanamachine wants to merge 1 commit into
elastic:9.0from
kibanamachine:backport/9.0/pr-244188

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.0:

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:49
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Nov 25, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

CI was triggered for this PR, but this PR targets 9.0 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 9.2
  • 9.1
  • 8.19
  • 7.17

1 similar comment
@elasticmachine
Copy link
Copy Markdown
Contributor

CI was triggered for this PR, but this PR targets 9.0 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 9.2
  • 9.1
  • 8.19
  • 7.17

auto-merge was automatically disabled November 25, 2025 18:52

Pull request was closed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants