{"id":3059,"date":"2026-08-30T22:15:25","date_gmt":"2026-08-31T02:15:25","guid":{"rendered":"https:\/\/csimmons.dev\/blog\/?p=3059"},"modified":"2026-08-30T22:16:21","modified_gmt":"2026-08-31T02:16:21","slug":"repairing-scheduled-tasks-after-a-coldfusion-migration","status":"publish","type":"post","link":"https:\/\/csimmons.dev\/blog\/2026\/08\/repairing-scheduled-tasks-after-a-coldfusion-migration\/","title":{"rendered":"Repairing Scheduled Tasks After a ColdFusion Migration"},"content":{"rendered":"

I recently ran into an issue with scheduled tasks after migrating an Adobe ColdFusion 2021 server to ColdFusion 2023. The server-level scheduled tasks were present in the ColdFusion Administrator, but none of them could be edited.<\/p>\n

Every attempt to save a task resulted in this error:<\/p>\n

\"ColdFusion
ColdFusion scheduled task invalid extension<\/figcaption><\/figure>\n

Troubleshooting the Error<\/h2>\n

I found an old Adobe Community thread describing the same error<\/a>. In that case, the scheduled task was supposed to save its output as an HTML file. The suggested solution was to stop ColdFusion, back up neo-cron.xml<\/code>, add the desired extension to its list of allowed output-file extensions, and restart ColdFusion.<\/p>\n

That solution made sense for a task that was intentionally producing a file, but none of my scheduled tasks were configured to save their output.<\/p>\n

I also found a more recent discussion about scheduled tasks not saving changes in ColdFusion 2021<\/a>. That thread covers an additional security requirement: when a scheduled task is configured to save its output to a file, the output directory may need to be whitelisted under schedulerexecutionpaths<\/code> in pathfilter.json<\/code>.<\/p>\n

Again, since I was not generating output, this was a dead end.<\/p>\n

The original neo-cron.xml<\/code> backup still contained the task definitions I needed, so I tried another approach. I cleared the scheduled tasks on the new server in the ColdFusion Administrator and used CommandBox’s CFConfig module to import only the scheduled-task settings:<\/p>\n

cfconfig import from=cf2021-export.json to=cf2023-server includeList=scheduledTasks<\/code><\/pre>\n
The includeList<\/code> limited the import to the scheduled tasks. They were recreated, but I still could not edit them.<\/p>\n
I created a new test task and confirmed that I could save and edit it. That worked, but recreating all of the scheduled tasks manually would have been tedious and would have made it easy to miss a URL, schedule, credential, proxy setting, or paused state.<\/p>\n
A New Tool: Scheduled Task Repair<\/h2>\n
I wanted a safer way to inspect the backup, compare it with the current scheduler, and choose exactly which tasks to rebuild.<\/p>\n
I put together a small utility called Scheduled Task Repair<\/a> to do exactly that.<\/p>\n
Instead of importing the scheduler configuration back into ColdFusion, the utility reads the task definitions and rebuilds the selected tasks using <cfschedule><\/code>.<\/p>\n
What It Does<\/h2>\n
Scheduled Task Repair provides a browser-based interface for uploading and reviewing a neo-cron.xml<\/code> file.<\/p>\n
The utility can:<\/p>\n