• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

CFSchedule dying at midnight

New Here ,
Aug 28, 2017 Aug 28, 2017

Copy link to clipboard

Copied

Conundrum - on both my CF 2016 Devlt and Production Servers a SERVER LEVEL CFSchedule Task that I have programatically created intermittently "dies" at midnight.  I have it scheduled to run every 60 seconds, but sometimes it seems to run at 11.59.something and then the CFSchedule "Next Run" date/time is set to a date/time far into the future.  For example, this is what the Scheduled Tasks Server Setting is now showing:

Interval 1min 0sec

Last Run: 8/28/2017 11:59:22PM

Next Run: 8/29/2017 6.38.22PM (??????????????????)

Repeat: -1

Remaining Count: Infinite

Cluster: NO

Here is the Code to boot off the CFSchedule Task:

<cfschedule action = "update"

task = "myTaskNameHere"

interval = "60"

url = "http:/xxx.com.au/sendMessages.cfm"

onMisfire = "FIRENOW"

onException = "REFIRE">

I am stumped.

Views

662

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Aug 29, 2017 Aug 29, 2017

Copy link to clipboard

Copied

Does the schedule.log show anything when the event fires?

I remember seeing a bug a while back with regard to the FIRENOW. Trying setting the task without it and see if it happens again.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 29, 2017 Aug 29, 2017

Copy link to clipboard

Copied

LATEST

nada -

29/08/2017  11:59:56 PM  Information  DefaultQuartzScheduler_Worker-5 

Task DEFAULT.nerivoSendMessages triggered.

and it happened again last night ...

I will remove onMisfire = "FIRENOW" and see what happens tonight - I recall putting it in there because of this problem, so I am not hopeful that this will fix it.

It really is odd.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Documentation