Here is an oldie with a new twist. We have many scheduled tasks on our CRM system. Many of them are batched and listed in a table we created which is called by the scheduled task manager at 8 specific times. Each subtask is fired off with cfmodule. We opted for this over chaining, partially because it wasn't available at the time (2005) and because we think its easier to manage. Though that's not the issue. We have one batch, where the first item called is a SQL Server Stored Procedure that runs about 90 minutes. Once or twice a month, the task manager will fire this task off a second time and corrupt that data. The Adobe CF log only shows it firing once, but our batch logic keeps a log, and it shows that it ran twice, as well as getting two confirmation emails. It is not every evening. It is not at a the same timespan into the run. It could be 5 minutes, it could be 20. I see articles out there where persons have complained of this happening, but its less random. Has anyone ever experienced something like this? Timeouts on these batches are set to 3 hours. We use the default retries=3 in all of our scheduled tasks, but this task has not failed. (Maybe CF thinks it has) I have a fix that I am going to put in place for it this evening. The running/idle state will be stored in the database, and if running a second thread will not be allowed to fire. I just feel like I should not have to do that.