[Triggers Actions UI] Wait for connectors list to filter in FTR searchConnectors helper

[kibanamachine]

Fixes #235623

Summary

• The Opsgenie connector FTR test asserted the connectors list had narrowed to 1 row but read 6, because the shared searchConnectors page-object helper returned before the client-side search filtered the table.
• The helper waited on .euiBasicTable[data-test-subj="actionsTable"]:not(.euiBasicTable-loading), whose loading class only tracks the initial data fetch — never EUI's debounced in-memory search — so it resolved instantly against the still-unfiltered table, and getConnectorsList() read all accumulated connectors.
• Replaced that wait with a bounded retry.waitFor that re-reads the rendered rows until they have all settled to match the search text. The search action (type + ENTER) is still issued once; only the DOM read is polled, so no interaction is retried.

Context

• Follows the root cause and fix proposed by the Failed Test Investigator (see the issue comment).
• Long-standing timing race, not a product bug: ~11 failures over 11 months, all on kibana-on-merge (local, not Cloud/serverless), spanning 9.1 → 8.19; the latest failure was 2026-08-19 on kibana-on-merge - 8.19.
• On main and 9.5 the Opsgenie FTR spec has been migrated/relocated to Scout, but the buggy shared helper still lives on main (used by apps/rules/details.ts) and on every open release branch — so the fix lands on main and backports to the branches where the Opsgenie FTR test still runs (9.4, 8.19).

Verification

Verified locally

✅ Passed: node scripts/eslint x-pack/platform/test/functional_with_es_ssl/page_objects/triggers_actions_ui_page.ts

Not verified locally

• FTR tests need a live Elasticsearch + Kibana and cannot run on this runner.
• The failing opsgenie.ts spec no longer exists on main (migrated to Scout), so it can only be exercised on the 9.4 / 8.19 release branches once this fix is backported; behavior under CI parallel load was not measured.

Backporting guidance

Applied backport:all-open. The shared triggers_actions_ui_page.ts helper exists byte-identically on every open release branch (9.5, 9.4, 8.19 per versions.json) and the patch applies unchanged. On 9.4 and 8.19 this directly fixes the flaky Opsgenie FTR spec; on 9.5 the Opsgenie spec has been relocated to Scout but the shared helper is still used by other FTR connector/rules tests, so the fix is a safe improvement there too.

Note

Share feedback in #kibana-qa. Mention @copilot to make quick changes.

Warning

Firewall blocked 3 domains

The following domains were blocked by the firewall during workflow execution:

• awmgmcpg
• iojs.org
• nodejs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"
    - "iojs.org"
    - "nodejs.org"

See Network Configuration for more information.

Generated by Flaky Test Fixer for #235623 · 285.6 AIC · ⌖ 21 AIC · ⊞ 10.7K · ◷

[kibanamachine]

/flaky ftrConfig:x-pack/platform/test/functional_with_es_ssl/apps/rules/config.ts:30

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Flaky Fix Verifier for #286190 · 242.4 AIC · ⌖ 45.6 AIC · ⊞ 11.4K · ◷

[kibanamachine]

🔍 Verifying the fix

This fix hardens the shared searchConnectors FTR page-object helper. The originally-flaky Opsgenie spec (#235623) no longer exists on main (migrated to Scout), so verification runs apps/rules/config.ts — whose details.ts spec is the remaining FTR consumer of the fixed helper on main — 30× to confirm the client-side search race is stable.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Flaky Fix Verifier for #286190 · 242.4 AIC · ⌖ 45.6 AIC · ⊞ 11.4K · ◷

[kibanamachine]

Flaky Test Runner

✅ Build triggered - kibana-flaky-test-suite-runner#13944

• x-pack/platform/test/functional_with_es_ssl/apps/rules/config.ts x30

[kibanamachine]

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#13944

[❌] x-pack/platform/test/functional_with_es_ssl/apps/rules/config.ts: 28/30 tests passed.

see run history

[kibanamachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 9758b93
• Build duration: 110 mins

Failed CI Steps

• FTR Configs #10
• FTR Configs #106
• FTR Configs #141

Metrics [docs]

Unknown metric groups

warm start memory

id	before	after	diff
post forced gc heap baseline	-	839839208	+839839208
post forced gc heap delta	-	-1500668	-1500668
post forced gc heap delta standard deviation	-	2598281	+2598281
post forced gc heap target	-	838338540	+838338540
tail heap delta	-	-34450145	-34450145
total			+1644825216

Test Failures

• [job] [logs] FTR Configs #141 / security app - login selector reset session page "after all" hook for "compare screenshot"
• [job] [logs] FTR Configs #141 / security app - login selector reset session page "before all" hook for "compare screenshot"

History

• 💛 Build #488629 was flaky 2e1a7f1

[kibanamachine]

Starting backport for target branches: 8.19, 9.4, 9.5

https://github.com/elastic/kibana/actions/runs/34621555273

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.19
✅	9.4
✅	9.5

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation