Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Issues
  • #1157
Closed
Open
Issue created Dec 13, 2018 by Administrator@rootContributor

Repeated job using "every" starts at the wrong time

Created by: ajwootto

Description

Hi, I'm adding a job to Bull like this:

bull.add(data, {
     delay: 600000,
     repeat: {
         every: 600000,
         jobId: "some_string"
     }
}

Basically the job should happen for the first time 10 minutes from the time this is called, and then repeat every 10 minutes thereafter.

If I call this at, say, 4:03 PM, the job is first processed at 4:10 PM and repeats every 10 minutes from that point on.

It seems that the "every" parameter is just ignoring the relative delay and just having the job repeat on the 10 minute marks of the hour. Is this expected behaviour or should it actually be happening at 4:13 PM, 4:23 PM and so on?

Assignee
Assign to
Time tracking