tracker issue : CF-3327936

select a category, or use search below
(searches all categories and all time range)

Scheduled Tasks not chaining

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/UserError

Reporter/Name(from Bugbase): / ext-user (Vamseekrishna Nanneboina)

Created: 09/10/2012

Components: Scheduler

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Mac 10 All,Win XP All

Vote Count: 0


Set up a series of chained scheduled tasks. When tested manually (by starting the first process from the admin), all three processes run but when the first process triggers at its daily time, it wont kick off the second chained process. No error is produced 

Additional Info:
Tried to trap the error by invoking an event handler on exception and misfire, but unable to get the scheduler to find the cfc regardless of the syxtax used. The site is setup as a subdomain for another site, but it is still a distinct site. Placed the CFC in the root of both the subdomain site and regular www site and tried several paths, but none seem to work. For example, the site is located in d:\web\\subDomain. Tried setting the event handler path as,, subDomain.handlerCFCName and handlerCFCName, and none worked

Link to forum thread -





----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3327936

External Customer Info:
External Company:  
External Customer Name:  
External Customer Email:



[on behalf of the user ggantzer2] Thank you for submitting this. The second portion of the bug related to trapping the error was solved, but the chaining remains an issue. For the second portion, a directory in the CFC path contained a “.”, such as “c:/site/ “, which could not be handled by the CF Admin. We mapped a new path in the administrator to correct this.
Comment by Vamseekrishna N.
18122 | September 10, 2012 08:45:39 AM GMT
We cannot have something like in the cfc path since we are providing the cfc path using the .[dot] notation. As a workaround we need to have a virtual directory configured for that path and use the virtual directory path to set the event handler.
Comment by Asha K.
18123 | April 18, 2013 07:19:47 AM GMT
Comment by Rupesh K.
18124 | August 22, 2013 12:39:10 AM GMT