How to make node-schedule work in Heroku?











up vote
3
down vote

favorite












I am running jobs from the 'node-schedule' module.



On localhost everything works great but when I upload to production in Heroku it doesn't.



i have changed my timezone in the settings -> var config to TZ at Asia/Jerusalem
but it still doesn't work.
Any idea why? Uploading my code although I think it is something with Heroku, not the code. Currently updating every minute just to test it, usefully its once every 1.5 hours 



const schedule = require("node-schedule");

const needle = require("needle");



let j = schedule.scheduleJob("* /1 * * * *", function() {

    needle.put("https://myserver.herokuapp.com/myendpoint");

});





node.js express heroku scheduled-tasks scheduler







share|improve this question






















  • seems like the scheduler is a add on: devcenter.heroku.com/articles/scheduler
    – split
    Nov 22 at 2:29










  • BTW changing your timezone on Heroku is only a visual change for the dashboard, I don't believe it actually reflects on the servers.
    – dotconnor
    Nov 22 at 2:32










  • This is not the add on scheduler from Heroku. It's a node package on npm
    – Contentop
    Nov 22 at 2:36










  • I think you have to check where/how the node package gets its info. I guess from the servers scheduler, and when its not present then.....EDIT: I have just checked - it use cron.
    – split
    Nov 22 at 2:39












  • Ok so if uses cron is should work right?
    – Contentop
    Nov 22 at 2:48















up vote
3
down vote

favorite












I am running jobs from the 'node-schedule' module.



On localhost everything works great but when I upload to production in Heroku it doesn't.



i have changed my timezone in the settings -> var config to TZ at Asia/Jerusalem
but it still doesn't work.
Any idea why? Uploading my code although I think it is something with Heroku, not the code. Currently updating every minute just to test it, usefully its once every 1.5 hours 



const schedule = require("node-schedule");

const needle = require("needle");



let j = schedule.scheduleJob("* /1 * * * *", function() {

    needle.put("https://myserver.herokuapp.com/myendpoint");

});





node.js express heroku scheduled-tasks scheduler







share|improve this question






















  • seems like the scheduler is a add on: devcenter.heroku.com/articles/scheduler
    – split
    Nov 22 at 2:29










  • BTW changing your timezone on Heroku is only a visual change for the dashboard, I don't believe it actually reflects on the servers.
    – dotconnor
    Nov 22 at 2:32










  • This is not the add on scheduler from Heroku. It's a node package on npm
    – Contentop
    Nov 22 at 2:36










  • I think you have to check where/how the node package gets its info. I guess from the servers scheduler, and when its not present then.....EDIT: I have just checked - it use cron.
    – split
    Nov 22 at 2:39












  • Ok so if uses cron is should work right?
    – Contentop
    Nov 22 at 2:48













up vote
3
down vote

favorite









up vote
3
down vote

favorite











I am running jobs from the 'node-schedule' module.



On localhost everything works great but when I upload to production in Heroku it doesn't.



i have changed my timezone in the settings -> var config to TZ at Asia/Jerusalem
but it still doesn't work.
Any idea why? Uploading my code although I think it is something with Heroku, not the code. Currently updating every minute just to test it, usefully its once every 1.5 hours 



const schedule = require("node-schedule");

const needle = require("needle");



let j = schedule.scheduleJob("* /1 * * * *", function() {

    needle.put("https://myserver.herokuapp.com/myendpoint");

});





node.js express heroku scheduled-tasks scheduler







share|improve this question













I am running jobs from the 'node-schedule' module.



On localhost everything works great but when I upload to production in Heroku it doesn't.



i have changed my timezone in the settings -> var config to TZ at Asia/Jerusalem
but it still doesn't work.
Any idea why? Uploading my code although I think it is something with Heroku, not the code. Currently updating every minute just to test it, usefully its once every 1.5 hours 



const schedule = require("node-schedule");

const needle = require("needle");



let j = schedule.scheduleJob("* /1 * * * *", function() {

    needle.put("https://myserver.herokuapp.com/myendpoint");

});





node.js express heroku scheduled-tasks scheduler




node.js express heroku scheduled-tasks scheduler






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 at 2:10









Contentop

226




226












  • seems like the scheduler is a add on: devcenter.heroku.com/articles/scheduler
    – split
    Nov 22 at 2:29










  • BTW changing your timezone on Heroku is only a visual change for the dashboard, I don't believe it actually reflects on the servers.
    – dotconnor
    Nov 22 at 2:32










  • This is not the add on scheduler from Heroku. It's a node package on npm
    – Contentop
    Nov 22 at 2:36










  • I think you have to check where/how the node package gets its info. I guess from the servers scheduler, and when its not present then.....EDIT: I have just checked - it use cron.
    – split
    Nov 22 at 2:39












  • Ok so if uses cron is should work right?
    – Contentop
    Nov 22 at 2:48


















  • seems like the scheduler is a add on: devcenter.heroku.com/articles/scheduler
    – split
    Nov 22 at 2:29










  • BTW changing your timezone on Heroku is only a visual change for the dashboard, I don't believe it actually reflects on the servers.
    – dotconnor
    Nov 22 at 2:32










  • This is not the add on scheduler from Heroku. It's a node package on npm
    – Contentop
    Nov 22 at 2:36










  • I think you have to check where/how the node package gets its info. I guess from the servers scheduler, and when its not present then.....EDIT: I have just checked - it use cron.
    – split
    Nov 22 at 2:39












  • Ok so if uses cron is should work right?
    – Contentop
    Nov 22 at 2:48
















seems like the scheduler is a add on: devcenter.heroku.com/articles/scheduler
– split
Nov 22 at 2:29




seems like the scheduler is a add on: devcenter.heroku.com/articles/scheduler
– split
Nov 22 at 2:29












BTW changing your timezone on Heroku is only a visual change for the dashboard, I don't believe it actually reflects on the servers.
– dotconnor
Nov 22 at 2:32




BTW changing your timezone on Heroku is only a visual change for the dashboard, I don't believe it actually reflects on the servers.
– dotconnor
Nov 22 at 2:32












This is not the add on scheduler from Heroku. It's a node package on npm
– Contentop
Nov 22 at 2:36




This is not the add on scheduler from Heroku. It's a node package on npm
– Contentop
Nov 22 at 2:36












I think you have to check where/how the node package gets its info. I guess from the servers scheduler, and when its not present then.....EDIT: I have just checked - it use cron.
– split
Nov 22 at 2:39






I think you have to check where/how the node package gets its info. I guess from the servers scheduler, and when its not present then.....EDIT: I have just checked - it use cron.
– split
Nov 22 at 2:39














Ok so if uses cron is should work right?
– Contentop
Nov 22 at 2:48




Ok so if uses cron is should work right?
– Contentop
Nov 22 at 2:48












1 Answer
1






active

oldest

votes

















up vote
1
down vote













I am successfully using cron jobs on Heroku and Azure with following code. I am using cron






import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()








share|improve this answer





















  • There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
    – shmit
    Nov 22 at 4:23










  • How does this work since heroku powers down idle nodes?
    – Notflip
    Nov 22 at 7:45






  • 1




    Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
    – shmit
    Nov 22 at 21:44













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422962%2fhow-to-make-node-schedule-work-in-heroku%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













I am successfully using cron jobs on Heroku and Azure with following code. I am using cron






import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()








share|improve this answer





















  • There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
    – shmit
    Nov 22 at 4:23










  • How does this work since heroku powers down idle nodes?
    – Notflip
    Nov 22 at 7:45






  • 1




    Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
    – shmit
    Nov 22 at 21:44

















up vote
1
down vote













I am successfully using cron jobs on Heroku and Azure with following code. I am using cron






import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()








share|improve this answer





















  • There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
    – shmit
    Nov 22 at 4:23










  • How does this work since heroku powers down idle nodes?
    – Notflip
    Nov 22 at 7:45






  • 1




    Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
    – shmit
    Nov 22 at 21:44















up vote
1
down vote










up vote
1
down vote









I am successfully using cron jobs on Heroku and Azure with following code. I am using cron






import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()








share|improve this answer












I am successfully using cron jobs on Heroku and Azure with following code. I am using cron






import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()  








import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()  





import { CronJob } from 'cron';



  const doSomething = new CronJob(

    '0 0 * * 1', //cron time

    fnname, //replace with your function that you want to call

    null, //oncomplete

    false, //start flag

    'America/Los_Angeles',// timezone

  );

  

  doSomething.start()






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 at 4:15









shmit

44239




44239












  • There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
    – shmit
    Nov 22 at 4:23










  • How does this work since heroku powers down idle nodes?
    – Notflip
    Nov 22 at 7:45






  • 1




    Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
    – shmit
    Nov 22 at 21:44




















  • There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
    – shmit
    Nov 22 at 4:23










  • How does this work since heroku powers down idle nodes?
    – Notflip
    Nov 22 at 7:45






  • 1




    Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
    – shmit
    Nov 22 at 21:44


















There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
– shmit
Nov 22 at 4:23




There is no need to set timezone on Heroku. The job run as per schedule and time zones are as per timezone defined at momentjs.com/timezone
– shmit
Nov 22 at 4:23












How does this work since heroku powers down idle nodes?
– Notflip
Nov 22 at 7:45




How does this work since heroku powers down idle nodes?
– Notflip
Nov 22 at 7:45




1




1




Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
– shmit
Nov 22 at 21:44






Its powers down only those dynos that are running under free tier. You canuse a service like uptime robot to ping those dynos intermittently that will keep them awake but this leads to fast consumption of free 550 dyno hours.
– shmit
Nov 22 at 21:44




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422962%2fhow-to-make-node-schedule-work-in-heroku%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more