[ResponseOps][Connectors] PagerDuty action fails with "Expected object, received string" for customDetails field#253683
Merged
georgianaonoleata1904 merged 4 commits intoelastic:mainfrom Feb 18, 2026
Conversation
georgianaonoleata1904
added
release_note:skip
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
georgianaonoleata1904
added
backport:version
…aonoleata1904/kibana into pd-custom-details-error
cnasikas
approved these changes
Feb 18, 2026
Member
cnasikas
left a comment
cnasikas
left a comment
There was a problem hiding this comment.
Tested and is working as expected!
Contributor
|
Starting backport for target branches: 9.3 |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]
|
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 18, 2026
…t, received string" for customDetails field (elastic#253683) Closes elastic#253665 ## Summary - The customDetails field was saved as a JSON string by the UI, but the backend schema expected an object, causing validation failures at rule execution time. - Wrap customDetailsSchema with `Coerced()` to automatically parse JSON strings into objects before validation. (cherry picked from commit 2637433)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Feb 18, 2026
… object, received string" for customDetails field (#253683) (#253714) # Backport This will backport the following commits from `main` to `9.3`: - [[ResponseOps][Connectors] PagerDuty action fails with "Expected object, received string" for customDetails field (#253683)](#253683) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2026-02-18T12:57:02Z","message":"[ResponseOps][Connectors] PagerDuty action fails with \"Expected object, received string\" for customDetails field (#253683)\n\nCloses https://github.com/elastic/kibana/issues/253665\n\n## Summary\n\n- The customDetails field was saved as a JSON string by the UI, but the\nbackend schema expected an object, causing validation failures at rule\nexecution time.\n- Wrap customDetailsSchema with `Coerced()` to automatically parse JSON\nstrings into objects before validation.","sha":"2637433885a8edfcca45c5e06610c10e43619fe3","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.4.0","v9.3.1"],"title":"[ResponseOps][Connectors] PagerDuty action fails with \"Expected object, received string\" for customDetails field","number":253683,"url":"https://github.com/elastic/kibana/pull/253683","mergeCommit":{"message":"[ResponseOps][Connectors] PagerDuty action fails with \"Expected object, received string\" for customDetails field (#253683)\n\nCloses https://github.com/elastic/kibana/issues/253665\n\n## Summary\n\n- The customDetails field was saved as a JSON string by the UI, but the\nbackend schema expected an object, causing validation failures at rule\nexecution time.\n- Wrap customDetailsSchema with `Coerced()` to automatically parse JSON\nstrings into objects before validation.","sha":"2637433885a8edfcca45c5e06610c10e43619fe3"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/253683","number":253683,"mergeCommit":{"message":"[ResponseOps][Connectors] PagerDuty action fails with \"Expected object, received string\" for customDetails field (#253683)\n\nCloses https://github.com/elastic/kibana/issues/253665\n\n## Summary\n\n- The customDetails field was saved as a JSON string by the UI, but the\nbackend schema expected an object, causing validation failures at rule\nexecution time.\n- Wrap customDetailsSchema with `Coerced()` to automatically parse JSON\nstrings into objects before validation.","sha":"2637433885a8edfcca45c5e06610c10e43619fe3"}},{"branch":"9.3","label":"v9.3.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgiana-Andreea Onoleață <georgiana.onoleata@elastic.co>
chrisbmar
pushed a commit
to chrisbmar/kibana
that referenced
this pull request
Feb 19, 2026
…t, received string" for customDetails field (elastic#253683) Closes elastic#253665 ## Summary - The customDetails field was saved as a JSON string by the UI, but the backend schema expected an object, causing validation failures at rule execution time. - Wrap customDetailsSchema with `Coerced()` to automatically parse JSON strings into objects before validation.
cnasikas
added
release_note:fix
and removed
release_note:skip
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Feb 19, 2026
…t, received string" for customDetails field (elastic#253683) Closes elastic#253665 ## Summary - The customDetails field was saved as a JSON string by the UI, but the backend schema expected an object, causing validation failures at rule execution time. - Wrap customDetailsSchema with `Coerced()` to automatically parse JSON strings into objects before validation.
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
4 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.
Closes #253665
Summary
Coerced()to automatically parse JSON strings into objects before validation.Release notes
Fix a bug with PagerDuty where setting the Custom details field will cause rules to fail.