elastic/kibana

[Response Ops][Reporting] Use `p-retry` to retry report

Open

#245437 opened on Dec 5, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Feature:Reporting:FrameworkTeam:ResponseOpsgood first issuequick-win

Description

We added retries within the reporting task to handle retries for scheduled reporting in this PR: https://github.com/elastic/kibana/pull/229998

We should consider switching to using the p-retry library to avoid bugs with custom code.

Contributor guide

Tech stack
typescriptnodejs
Domain
backend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.js async/awaitp retry libraryKibana reporting module
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review the existing retry logic in the reporting task, which was added in PR https://github.com/elastic/kibana/pull/229998. Understand how p retry works by reading its documentation. Then, replace the custom retry code with p retry, ensuring that retry behavior (backoff, count) is preserved. Test the change to verify that scheduled reports are retried correctly. Check the comments on this issue for any additional guidance from maintainers.