h3ravel/framework

Feature: Implement failed job handling and storage strategy

Open

#93 opened on Jan 23, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (14 forks)auto 404
@h3ravel/contracts@h3ravel/queuebackground-jobsenhancementglobal-typesgood first issue

Repository metrics

Stars
 (22 stars)
PR merge metrics
 (PR metrics pending)

Description

Description: Define how failed jobs are tracked, stored, and optionally retried.

This should align with Laravel’s failed job philosophy without copying it directly.

Goals:

  • Capture failure reason & stack trace
  • Store failed jobs (Redis / DB – pluggable)
  • Allow retrying failed jobs
  • Allow clearing failed jobs

Acceptance Criteria:

  • Failed jobs are persisted
  • Retry flow is defined
  • Storage backend is configurable

Contributor guide

Research direction
Explore existing failed job handling patterns (e.g., Laravel, Bull) and design pluggable storage interfaces. Implement in memory/Redis/DB adapters and retry logic.
Tech stack
typescript
Domain
backend
Issue type
Feature
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptRedis or SQL basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60