{"action":"created","issue":{"url":"https://api.github.com/repos/dbader/schedule/issues/83","repository_url":"https://api.github.com/repos/dbader/schedule","labels_url":"https://api.github.com/repos/dbader/schedule/issues/83/labels{/name}","comments_url":"https://api.github.com/repos/dbader/schedule/issues/83/comments","events_url":"https://api.github.com/repos/dbader/schedule/issues/83/events","html_url":"https://github.com/dbader/schedule/issues/83","id":148348524,"number":83,"title":"Job not running","user":{"login":"kc-hyperaxes","id":5015206,"avatar_url":"https://avatars.githubusercontent.com/u/5015206?v=3","gravatar_id":"","url":"https://api.github.com/users/kc-hyperaxes","html_url":"https://github.com/kc-hyperaxes","followers_url":"https://api.github.com/users/kc-hyperaxes/followers","following_url":"https://api.github.com/users/kc-hyperaxes/following{/other_user}","gists_url":"https://api.github.com/users/kc-hyperaxes/gists{/gist_id}","starred_url":"https://api.github.com/users/kc-hyperaxes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kc-hyperaxes/subscriptions","organizations_url":"https://api.github.com/users/kc-hyperaxes/orgs","repos_url":"https://api.github.com/users/kc-hyperaxes/repos","events_url":"https://api.github.com/users/kc-hyperaxes/events{/privacy}","received_events_url":"https://api.github.com/users/kc-hyperaxes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-04-14T12:41:38Z","updated_at":"2016-07-12T12:49:03Z","closed_at":null,"body":"There is one task out of several that is not running or getting scheduled for its next run incorrectly.\r\nThe task 'catalog_export' typically runs for 90-120 minutes so the start is occurs on one day at it finishes on the next day. We run it on the staging environment at 3am and it has never failed to run correctly, so I am wondering if the start date being different from the end date could be a factor. \r\n\r\nBefore enabling schedule logging it failed twice. The pattern was that it ran successfully on the initial run, failed to run on the next night, ran sucessfully on the following (third) night, and then failed to run again on the fourth night.\r\n\r\nThe code says:\r\n`schedule.every().day.at(\"23:25\").do(catalog_export)\r\n`\r\nAnd it appears in the log:\r\n\r\n> 2016-04-11 23:25:00,334 = schedule - INFO - Running job Every 1 day at 23:25:00 do catalog_export() (last run: [never], next run: 2016-04-11 23:25:00)\r\n\r\nHere is one that worked without incident and was scheduled before catalog_export and ran the next day without incident.\r\n\r\n> 2016-04-11 23:15:00,397 = schedule - INFO - Running job Every 1 day at 23:15:00 do customerAlias_load() (last run: [never], next run: 2016-04-11 23:15:00)\r\n> \r\n> 2016-04-12 23:15:00,048 = schedule - INFO - Running job Every 1 day at 23:15:00 do customerAlias_load() (last run: 2016-04-11 23:16:55, next run: 2016-04-12 23:15:00)\r\n> \r\n\r\nBut there is nothing in the log for catalog_export on 2016-04-12, 23:25 is just silent.\r\n\r\n2016-04-12 23:16:51,927 = cat2es.customerAlias_load - INFO - finished at: 23:16:51 \r\n2016-04-12 23:57:24,667 = schedule - INFO - Running job Every 60 minutes do heartbeat() (last run: 2016-04-12 22:57:24, next run: 2016-04-12 23:57:24)\r\n\r\nThere are two logs attached.\r\nIn the log for 20160411:\r\nbetween lines 22-23: catalog_export fails to run\r\nline 34: schedule log enabled\r\nline 96: catalog_export starts, and is rescheduled\r\n\r\nin the log for 20160412:\r\nbetween lines 20-31: catalog_export fails to run\r\n\r\n[cat2es_20160412_log.txt](https://github.com/dbader/schedule/files/219101/cat2es_20160412_log.txt)\r\n[cat2es_20160411_log.txt](https://github.com/dbader/schedule/files/219102/cat2es_20160411_log.txt)\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/dbader/schedule/issues/comments/232036958","html_url":"https://github.com/dbader/schedule/issues/83#issuecomment-232036958","issue_url":"https://api.github.com/repos/dbader/schedule/issues/83","id":232036958,"user":{"login":"kc-hyperaxes","id":5015206,"avatar_url":"https://avatars.githubusercontent.com/u/5015206?v=3","gravatar_id":"","url":"https://api.github.com/users/kc-hyperaxes","html_url":"https://github.com/kc-hyperaxes","followers_url":"https://api.github.com/users/kc-hyperaxes/followers","following_url":"https://api.github.com/users/kc-hyperaxes/following{/other_user}","gists_url":"https://api.github.com/users/kc-hyperaxes/gists{/gist_id}","starred_url":"https://api.github.com/users/kc-hyperaxes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kc-hyperaxes/subscriptions","organizations_url":"https://api.github.com/users/kc-hyperaxes/orgs","repos_url":"https://api.github.com/users/kc-hyperaxes/repos","events_url":"https://api.github.com/users/kc-hyperaxes/events{/privacy}","received_events_url":"https://api.github.com/users/kc-hyperaxes/received_events","type":"User","site_admin":false},"created_at":"2016-07-12T12:49:03Z","updated_at":"2016-07-12T12:49:03Z","body":"I tried using multiple threads as a workaround but it did not work either. I had to switch to APScheduler to fix this issue."}}
{"actor":{"display_login":"kc-hyperaxes"}}