hasura / hasura/graphql-engine

Support Event Trigger Retry Logic

Open
#10,508 0 comments 0 reactions 0 assignees View on GitHub
a/eventing/data-triggers c/server c/v2-engine k/enhancement v2 v2-server
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Component

Event Triggers

### Is your proposal related to a problem?

Currently, the configuration for retries allows for setting a fixed number of retries and a specified delay between them. However, it lacks support for exponential backoff, which could be crucial in scenarios where a webhook might encounter issues or latency.

### Describe the solution you'd like

Requesting support for a multiplier or backoff algorithm to allow the configuration of a threshold that would be respected before initiating retries. This approach would prevent exhausting all retry attempts within a short time frame and enhance the likelihood of successfully processing the event.

Contributor guide

Open the contributing guide

Research direction

Start by locating the Event Triggers retry configuration and its existing fixed retry and delay behavior. No file or test is named; clarify the multiplier or backoff configuration, its retry semantics, and the tests needed to verify delayed retries before implementation.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.