Matt Aitken
de302858f8
* Started building out the docs navigation * Drafted out a lot of the docs pages. With just titles and descriptions with a coming soon message for now. * A ton more scaffolded pages with titles, descriptions, coming soon/incomplete docs messages * Created the remaining page stubs * Introduction page improvements * Lots of docs changes, mostly the task overview page * Moved some bits around * Task overview fleshed out * Triggering docs page * Regular task page * CLi dev docs * Docs for debugging locally * Environment variables docs * Added env var images * Deployment guides * Updated the title of “Integrations” to “Deployment integrations” to make it less confusing * Lots more docs pages * Changed the language to JavaScript * Fixed typos about queues and added a simple code sample * Moved the local debugger docs into the CLI dev page * Added the CLI deploy options * Delete the local debugger page * Updated the logging page with structured logging * Added the new CLI deploy options * Change to h4 for one of the options * Errors page * WIP on retrying * Retrying guide * Wait docs pages * Queuing docs simplified, partial written * Queuing and concurrency docs * Run tests docs * New combined error and retrying page * Errors and retrying page updated * More docs * Added a possible configurations coming soon table * Created a limits page * Added warnings about how you need to get early access * Minor fixes for the docs
27 lines
3.2 KiB
Plaintext
27 lines
3.2 KiB
Plaintext
---
|
|
title: "Writing tasks: Introduction"
|
|
sidebarTitle: "Introduction"
|
|
description: "Tasks are the core of Trigger.dev. They are long-running processes that are triggered by events."
|
|
---
|
|
|
|
Before digging deeper into the details of writing tasks, you should read the [fundamentals of tasks](/v3/tasks-overview) to understand what tasks are and how they work.
|
|
|
|
## Writing tasks
|
|
|
|
| Topic | Description |
|
|
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------- |
|
|
| [Logging](/v3/logging) | View and send logs and traces from your tasks. |
|
|
| [Errors & retrying](/v3/errors-retrying) | How to deal with errors and write reliable tasks. |
|
|
| [Wait](/v3/wait) | Wait for periods of time or for external events to occur before continuing. |
|
|
| [Concurrency & Queues](/v3/queue-concurrency) | Configure what you want to happen when there is more than one run at a time. |
|
|
| [Versioning](/v3/versioning) | How versioning works. |
|
|
| [Machines](/v3/machines) | Configure the CPU and RAM of the machine your task runs on |
|
|
| [Idempotency](/v3/idempotency) | Protect against mutations happening twice. |
|
|
| [Reattempting & Replaying](/v3/reattempting-replaying) | You can reattempt a task that has failed all of its attempts. You can also replay a task with a new version of your code. |
|
|
| [Notifications](/v3/notifications) | Send realtime notifications from your task that you can subscribe to from your backend or frontend. |
|
|
| [Rollbacks](/v3/rollbacks) | Rollback code inside a task when errors happen to provide transactional guarantees. |
|
|
| [Using APIs](/v3/using-apis) | How to use APIs from within your tasks. |
|
|
| [Trigger filters](/v3/trigger-filters) | Prevent unwanted filters where the payload doesn't match your filter. |
|
|
| [Middleware](/v3/middleware) | Middleware can wrap the task run function. |
|
|
| [Automated tests](/v3/automated-tests) | Write automated tests in code. |
|