> Suggestion for those with email jobs tied to scheduler. It maybe useful to > have some code to check that the email only get sent once.
To be honest, this should probably be built into any code that causes problems if it runs more than once. For instance, in your case, it's bad if an email is sent twice. It could be a billing job that would cause problems if it charged twice etc. In some ways that should be in the requirements for the code, and thus the tests. For instance, I have invoicing jobs that run every hour, but 99% of the time will decide to do nothing, but they run that frequently to ensure the timeliness of an invoice when one is required. N -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
