> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/v6.x/intro/release-history/whats-new-with-6.4.0.md). # What's New With 6.4.0 ColdBox 6.4.0 is more of a major than a minor release due to the amount of work we have done to bring you one of the most revolutionary features of this framework: **Scheduled Tasks.** ### ColdBox Scheduled Tasks Scheduled tasks have always been a point of soreness for many developers in *ANY* language. Especially choosing where to place them for execution: should it be cron? windows task scheduler? ColdFusion engine? Jenkins, Gitlab? and the list goes on and on. ![ColdBox Scheduled Tasks](https://825821834-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LA-UVvJIdbk5Kfk3bDs%2F-MYM-nAfGv_AQRLRbtg2%2F-MYMUHow0jE5L-BJFmkO%2FColdBoxScheduler.png?alt=media\&token=3f2ee504-d17d-4cf6-99df-854eaad55a36) The *ColdBox Scheduled Tasks* offers a fresh, programmatic and human approach to scheduling tasks on your server and multi-server application. It allows you to define your tasks in a portable **Scheduler** we lovingly call the `Scheduler.cfc` which not only can be used to define your tasks, but also monitor all of their life-cycles and metrics of tasks. Since ColdBox is also hierarchical, it allows for every single ColdBox Module to also define a `Scheduler` and register their own tasks as well. This is a revolutionary approach to scheduling tasks in an HMVC application. You can learn all about them in our two sections: * [CFML Scheduled Tasks](/v6.x/digging-deeper/promises-async-programming/scheduled-tasks.md) * [ColdBox Scheduled Tasks](/v6.x/digging-deeper/scheduled-tasks.md) ### Release Notes {% tabs %} {% tab title="ColdBox HMVC" %} **Bugs** * [COLDBOX-991](https://ortussolutions.atlassian.net/browse/COLDBOX-991) Fixes issues with Adobe losing App Context in Scheduled Tasks. You can now run scheduled tasks in Adobe with full app support. * [COLDBOX-988](https://ortussolutions.atlassian.net/browse/COLDBOX-988) When running scheduled tasks in ACF loading of contexts produce a null pointer exception * [COLDBOX-981](https://ortussolutions.atlassian.net/browse/COLDBOX-981) `DataMarshaller` no longer accepts 'row', 'column' or 'struct' as a valid argument. **Improvements** * [COLDBOX-998](https://ortussolutions.atlassian.net/browse/COLDBOX-998) Convert util to script and optimize * [COLDBOX-989](https://ortussolutions.atlassian.net/browse/COLDBOX-989) Add more debugging when exceptions occur when loading/unloading thread contexts * [COLDBOX-971](https://ortussolutions.atlassian.net/browse/COLDBOX-971) Implement caching strategy for application helper lookups into the `default` cache instead of the `template` cache. **New Features** * [COLDBOX-999](https://ortussolutions.atlassian.net/browse/COLDBOX-999) New `SchedulerService` that mointors and registers application scheduled tasks in an HMVC fashion * [COLDBOX-997](https://ortussolutions.atlassian.net/browse/COLDBOX-997) Added out and error stream helpers to Scheduled Tasks for better debugging * [COLDBOX-996](https://ortussolutions.atlassian.net/browse/COLDBOX-996) `newTask`() method on scheduled executor to replace nameless `newSchedule` * [COLDBOX-995](https://ortussolutions.atlassian.net/browse/COLDBOX-995) New scheduler object to keep track and metrics of registered tasks * [COLDBOX-994](https://ortussolutions.atlassian.net/browse/COLDBOX-994) New Scheduled Task with life-cycles and metrics * [COLDBOX-993](https://ortussolutions.atlassian.net/browse/COLDBOX-993) New async.time package to deal with periods, durations, time offsets and so much more * [COLDBOX-992](https://ortussolutions.atlassian.net/browse/COLDBOX-992) Added CFML Duration and Periods to async manager so task executions can be nicer and pin point accuracy * [COLDBOX-990](https://ortussolutions.atlassian.net/browse/COLDBOX-990) Allow structs for query strings when doing relocations * [COLDBOX-987](https://ortussolutions.atlassian.net/browse/COLDBOX-987) Encapsulate any type of exception in the REST Handler in a `onAnyOtherException`() action which can also be overidden by concrete handlers * [COLDBOX-986](https://ortussolutions.atlassian.net/browse/COLDBOX-986) Add registration and activation timestamps to the a module configuration object for active profiling. * [COLDBOX-985](https://ortussolutions.atlassian.net/browse/COLDBOX-985) Rename `renderLayout()` to just `layout()` and deprecate it for v7 * [COLDBOX-984](https://ortussolutions.atlassian.net/browse/COLDBOX-984) Rename `renderView(`) to just `view()` and deprecate it for v7 {% endtab %} {% tab title="WireBox" %} #### Bugs * [WIREBOX-112](https://ortussolutions.atlassian.net/browse/WIREBOX-112) virtual inheritance causes double `inits` on objects that do not have a constructor and their parent does. * [WIREBOX-95](https://ortussolutions.atlassian.net/browse/WIREBOX-95) `onDIComplete`() is called twice using virtual inheritance #### New Features * [WIREBOX-114](https://ortussolutions.atlassian.net/browse/WIREBOX-114) New coldbox dsl => `coldbox:appScheduler` which gives you the `appScheduler@coldbox` instance * [WIREBOX-113](https://ortussolutions.atlassian.net/browse/WIREBOX-113) new injection dsl: `wirebox:asyncManager` {% endtab %} {% endtabs %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://coldbox.ortusbooks.com/v6.x/intro/release-history/whats-new-with-6.4.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.