Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add delay between retry #24

Closed
amitava82 opened this issue Oct 5, 2018 · 8 comments
Closed

Add delay between retry #24

amitava82 opened this issue Oct 5, 2018 · 8 comments

Comments

@amitava82
Copy link

I'm trying to figure out how to add delay between retry on error. Neither setScheduledPeriod or
setScheduledDelay seems to do it. I want to retry a .job n number of times only on failure and there must be 10 minutes delay between retry. Is this possible to do?

@weyoss
Copy link
Owner

weyoss commented Oct 8, 2018

Both setScheduledPeriod and setScheduledDelay work for scheduling messages and not for setting up message retry delay upon failure.

A new parameter messageRetryDelay, allowing to wait for an amount of time before retrying a failed message, will be introduced in the next release.

Thank you for reporting this issue.

@weyoss
Copy link
Owner

weyoss commented Oct 8, 2018

A new release is out.

@weyoss
Copy link
Owner

weyoss commented Oct 8, 2018

Closing as resolved.

@weyoss weyoss closed this as completed Oct 8, 2018
@blurp1478963
Copy link

hello @weyoss
I have a bug whith the messageRetryDelay params:

new Message()
      .setRetryThreshold(3)
      .setRetryDelay(10)
      .setBody(this.message);

The first attempt comes à 0,
The second and the third comes 10 sec laters but quite together... there's no more 10 sec delay between attempts...

Capture d’écran 2019-09-06 à 11 28 30

any idea?

Thanks by advance

@elribonazo
Copy link

Same issue here, after a task has been failed it does not respect the retryDelay.

@elribonazo
Copy link

@weyoss Can you please re-open issue.

@weyoss
Copy link
Owner

weyoss commented Nov 29, 2019

@elribonazo @elribonazo @blurp1478963 Reopening the issue for investigation.

@weyoss weyoss reopened this Nov 29, 2019
@weyoss weyoss added the bug label Nov 29, 2019
@weyoss
Copy link
Owner

weyoss commented Nov 29, 2019

The issue has been fixed.

Please upgrade to the latest release!

@weyoss weyoss closed this as completed Nov 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants