{"action":"closed","issue":{"url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/270","repository_url":"https://api.github.com/repos/vsivsi/meteor-job-collection","labels_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/270/labels{/name}","comments_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/270/comments","events_url":"https://api.github.com/repos/vsivsi/meteor-job-collection/issues/270/events","html_url":"https://github.com/vsivsi/meteor-job-collection/issues/270","id":314407747,"node_id":"MDU6SXNzdWUzMTQ0MDc3NDc=","number":270,"title":"Job 'after' field set at the wrong time","user":{"login":"tanase-sebastian","id":1770484,"node_id":"MDQ6VXNlcjE3NzA0ODQ=","avatar_url":"https://avatars1.githubusercontent.com/u/1770484?v=4","gravatar_id":"","url":"https://api.github.com/users/tanase-sebastian","html_url":"https://github.com/tanase-sebastian","followers_url":"https://api.github.com/users/tanase-sebastian/followers","following_url":"https://api.github.com/users/tanase-sebastian/following{/other_user}","gists_url":"https://api.github.com/users/tanase-sebastian/gists{/gist_id}","starred_url":"https://api.github.com/users/tanase-sebastian/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tanase-sebastian/subscriptions","organizations_url":"https://api.github.com/users/tanase-sebastian/orgs","repos_url":"https://api.github.com/users/tanase-sebastian/repos","events_url":"https://api.github.com/users/tanase-sebastian/events{/privacy}","received_events_url":"https://api.github.com/users/tanase-sebastian/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-04-15T11:34:36Z","updated_at":"2018-10-09T07:58:07Z","closed_at":"2018-10-09T07:58:07Z","author_association":"NONE","body":"Hello,\r\n\r\nI was trying to create jobs using with delay(1000), so that they will run immediatly. However, what happened is that the 'after' field was set to about 41 minutes in the future, instead of 1 second. This happened all of a sudden, while previous job scheduling worked fine; I did not restart meteor nor did I change the system date in between.\r\n\r\nWhat's more, in the logs, the 'Constructed' message is set at the wrong time whereas the 'Job submitted' is set at the correct time.\r\n\r\nI attached a screenshot of the Job data in the DB. As you can see the 'created' field is set to '2018-04-13 16:45:32.421' and the 'after' field is set to '2018-04-13 17:27:18.300' when it should have been set to something like '2018-04-13 16:45:34.000'.\r\n\r\n![job_fields](https://user-images.githubusercontent.com/1770484/38777948-1b85abaa-40b1-11e8-905c-39c7001bb44a.png)\r\nDo you have any pointers on what could have gone wrong ?\r\n\r\nFor now, I think I will use after() instead of delay() and calculate the date myself."}}
{"actor":{"display_login":"tanase-sebastian"}}