Skip to content

Unexpected behavior with manual retries from Delayed Queue #222

@xelzi

Description

@xelzi

I am having issues when I try to manually retry a job in the Delayed Queue using Trigger.

Instead of this job retrying -- a new job is being created. This new job also nests the original parameters in a way that guarantees the retry will fail 😅

The Original Job -- has an id of 35:

Screen Shot 2020-05-21 at 5 27 26 PM

The New Job -- includes the original job id of 35 and nests the parameters ❓ ❓ ❓ :

Screen Shot 2020-05-21 at 5 28 41 PM

Expected Behavior

  1. No duplicated Job is created
  2. The retry count on the original job is iterated on

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions