Recurring jobs of an unregistered type keep firing and dead-lettering

Abierto
#3,276 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start with src/FluentCMS.Core/Jobs/RecurringJobs.cs, especially RecurringJobs.FireDueAsync at the lines cited in the issue, and trace how recurring jobs are registered, scheduled, and retried. The proposal leaves choices open for handling unregistered types and malformed payloads, so confirm the intended behavior with maintainers before implementing. Done means unregistered types create no new jobs and do not consume attempts on instances that do not know them.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:jobs type:bug

Problem

RecurringJobs.FireDueAsync (src/FluentCMS.Core/Jobs/RecurringJobs.cs:54,92) never checks the job registry, and no code removes a recurring row. After a plugin is removed, its per-minute job makes about 1,440 dead-lettered jobs a day, each with activity and outbox rows; an unknown type also burns attempts on an old instance during a rolling deploy.

Proposal

Skip (and log once) or disable recurring rows whose type is unregistered; release unknown types without using an attempt and dead-letter them only after an orphan age; treat bad payloads as non-retryable.

Acceptance

  • A recurring job of an unregistered type makes no new jobs
  • An unknown type does not use attempts on an instance that does not know it

Found in the code review of 17 Nov 2026 (B5).

Lenguaje dominante
C#
Estrellas
569
Forks
107
Merge medio
2 h 49 min
PR fusionados (30 d)
397

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.