elastic/kibana

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

Open

#245,437 opened on Dec 5, 2025

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

Repository metrics

Stars
 (19,065 stars)
PR merge metrics
 (Avg merge 2d 3h) (1,000 merged PRs in 30d)

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

Research direction
Review the custom retry logic in the reporting task (PR #229998) and replace it with the p retry library.
Tech stack
typescript
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80