Hi,

I'm sorry for the mix up with October invoices.  We're aware of the issue 
and are fixing it.  No cards have been charged yet, and we won't do so 
until we're confident that the invoice numbers are correct.

Thanks,
Vault Team.

On Thursday, November 8, 2012 11:47:34 AM UTC-8, iamtheschmitzer wrote:
>
> Me too - most of my scheduler charges for the month were on Oct 30.
>
> On Thu, Nov 8, 2012 at 1:46 PM, David Hall <pette...@gmail.com<javascript:>
> > wrote:
>
>> I do see an increase from 0.001 to 0.563 dyno hours for October 30th 
>> compared to previous days in the month on the app that use scheduler here 
>> as well.
>>
>> / David
>>
>> On Thu, Nov 8, 2012 at 8:08 PM, Josh Cronemeyer 
>> <joshuacr...@gmail.com<javascript:>
>> > wrote:
>>
>>> My monthly billing statement is what tipped me off to the problem, but 
>>> unfortunately my logs don't go back to Oct. 30.  I have verified that in 
>>> the past week my scheduled tasks are running in less than a second, at 10 
>>> minute intervals.  The fact that 3 separate codebases across 2 different 
>>> user accounts have the same spike on the same day is what made me think 
>>> this wasn't something I was doing wrong.
>>>
>>> I hadn't thought to set a max execution time for my scheduled processes 
>>> though, and i'm going to do that going forward.  Great suggestion.
>>>
>>>
>>> On Thursday, November 8, 2012 10:53:01 AM UTC-8, Neil Middleton wrote:
>>>>
>>>> Have you ascertained that your scheduled tasks aren't taking longer 
>>>> than normal for some reason?  Do you have maximum execution times set in 
>>>> your code to stop them running indefinitely?
>>>>
>>>> Neil
>>>>
>>>> On Thursday, November 8, 2012, Josh Cronemeyer wrote:
>>>>
>>>>> I've got access to two separate heroku accounts (mine and my 
>>>>> employer).  And several different apps across both accounts that use the 
>>>>> basic scheduler add on.  I've noticed on my Oct. bill that there is a 
>>>>> huge 
>>>>> spike in usage for all these apps and accounts on Oct. 30.  In all of 
>>>>> these 
>>>>> cases, the amount of processing done by the scheduler is not a function 
>>>>> of 
>>>>> traffic so any spike is unexpected.
>>>>>
>>>>> Is anyone else seeing a similar thing on their bill?  I noticed that 
>>>>> apps that just run a nightly scheduler the net effect is relatively 
>>>>> small, 
>>>>> but if you have scheduler tasks that run every 10 minutes the cost for 
>>>>> that 
>>>>> one anomalous day is pretty big.  My app that schedules every 10 minutes 
>>>>> went from an average 0.04 dynos to almost 6 dynos on Oct. 30.
>>>>>
>>>>> I've filed a support ticket on heroku, but was interested to see if 
>>>>> other folks were seeing the same issue.
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Heroku" group.
>>>>>  
>>>>> To unsubscribe from this group, send email to
>>>>> heroku+unsubscribe@**googlegroups.com
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/**group/heroku?hl=en_US?hl=en<http://groups.google.com/group/heroku?hl=en_US?hl=en>
>>>>>
>>>>  -- 
>>> You received this message because you are subscribed to the Google
>>> Groups "Heroku" group.
>>>  
>>> To unsubscribe from this group, send email to
>>> heroku+un...@googlegroups.com <javascript:>
>>> For more options, visit this group at
>>> http://groups.google.com/group/heroku?hl=en_US?hl=en
>>>
>>> -- 
>>> David Hall, M. Sc., da...@dpg.se
>>> +46 (0)708-39 62 91
>>>
>>>  <http://groups.google.com/group/heroku?hl=en_US?hl=en>
>>>
>>  -- 
>> You received this message because you are subscribed to the Google
>> Groups "Heroku" group.
>>  
>> To unsubscribe from this group, send email to
>> heroku+un...@googlegroups.com <javascript:>
>> For more options, visit this group at
>> http://groups.google.com/group/heroku?hl=en_US?hl=en
>>
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

Reply via email to