> For the complete documentation index, see [llms.txt](https://brightercommand.gitbook.io/paramore-brighter-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler.md). # Scheduler - [Scheduler](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport.md): In distributed applications, it is often necessary to schedule messages for deferred execution—whether for implementing delayed workflows, retry mechanisms, or time-based business processes. - [InMemory Scheduler](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport/inmemoryscheduler.md): The InMemory Scheduler is a lightweight, timer-based scheduling implementation provided by Brighter for testing, development, and demonstration purposes. - [Hangfire](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport/hangfirescheduler.md): Hangfire is one of the most widely used background job processing libraries in the .NET community, featuring a built-in monitoring dashboard. - [Quartz](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport/quartzscheduler.md): Quartz.NET is one of the most widely used enterprise-grade scheduling libraries in the .NET community. - [TickerQ](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport/tickerqscheduler.md): TickerQ is a high-performance, reflection-free background task scheduler for .NET that uses source generators. - [Aws Scheduler](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport/awsscheduler.md): AWS EventBridge Scheduler is a fully managed, serverless service on AWS that allows you to create, run, and manage scheduled tasks at scale. - [Azure Scheduler](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/brighterschedulersupport/azurescheduler.md): Azure Service Bus includes native support for scheduled message delivery using the ScheduledEnqueueTimeUtc property. - [Scheduling a Message](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/schedulingamessage.md): This page shows you how to schedule a message or request for deferred execution, how to cancel one you have already scheduled, and how to configure each scheduler for the job. - [Switching Schedulers](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/switchingschedulers.md): This page shows you how to move an existing application from one Brighter scheduler to another. - [Custom Scheduler](https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler/customscheduler.md): To add support for a different scheduler provider, implement the appropriate interfaces based on your use case. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://brightercommand.gitbook.io/paramore-brighter-documentation/scheduler.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.