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

Delayed job shows always in horizon the current timestamp #906

Closed
stefanbauer opened this issue Oct 9, 2020 · 1 comment · Fixed by #907
Closed

Delayed job shows always in horizon the current timestamp #906

stefanbauer opened this issue Oct 9, 2020 · 1 comment · Fixed by #907

Comments

@stefanbauer
Copy link

stefanbauer commented Oct 9, 2020

  • Horizon Version: 4.3.5
  • Laravel Version: 7.26.1
  • PHP Version: 7.4.10
  • Redis Driver & Version: predis 1.1.4
  • Database Driver & Version: MySQL 5.7

Description:

If you go to your horizon dashboard, click on the pending jobs item and select a pending job, you'll see an overview like this:

image

I'd expect that within the "Delayed Until" field there is the timestamp when the job should be executed. But it shows always the current timestamp. Refresh the page and you can see that it refreshes always to the current timestamp.

Here's a better screenshot. This job was already executed and it's already completed, but still the delay until refreshing (in the future which doesn't make sense though)

image

Steps To Reproduce:

  • Queue a delayed job with any delay (e.g. 1 hour)
  • Go to your horizon dashboard and check the delayed jobs
  • You won't see the correct "delayed until" timestamp (queuing + delay), but you see the current timestamp.
@driesvints
Copy link
Member

Hey @stefanbauer can you please try this in Horizon 5? We're not maintaining 4.x anymore. Feel free to report back when you've managed to reproduce it in 5.x

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants