nicktrn
8e6eb4f6d8
* lint and action updates * add custom image tag action * remove publish infra bloat * replace cancel action with native concurrency control * ignore all docs changes for release trigger * image action updates * update publish trigger paths * simplify semver checks * make it possible to call publish * add tests for custom action * rename publish workflows * call publish after successful package release * fix inputs and published package parsing * clarify image tag action errors * move test action * add test events * add changesets action mock * add docs checks * add github action test readme * fix docs check on push * update action versions in docs * cache npm for docs check * pretend to fix bad docs link * fix docs link * Revert "fix docs link" This reverts commita7508f5d55. * Revert "Revert "fix docs link"" This reverts commitec642af3dc. * improve caching * disable automatic publishing after release * limit docs checks to pushes to main and PRs * fix broken links * prevent word splitting and globbing * use latest checkout action everywhere * correctly detect prereleases as valid semver * update to latest cache action
22 lines
2.3 KiB
Plaintext
22 lines
2.3 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](/tasks/overview) to understand what tasks are and how they work.
|
|
|
|
## Writing tasks
|
|
|
|
| Topic | Description |
|
|
| :---------------------------------------------------| :------------------------------------------------------------------------------------------------------------------------ |
|
|
| [Logging](/logging) | View and send logs and traces from your tasks. |
|
|
| [Errors & retrying](/errors-retrying) | How to deal with errors and write reliable tasks. |
|
|
| [Wait](/wait) | Wait for periods of time or for external events to occur before continuing. |
|
|
| [Concurrency & Queues](/queue-concurrency) | Configure what you want to happen when there is more than one run at a time. |
|
|
| [Versioning](/versioning) | How versioning works. |
|
|
| [Machines](/machines) | Configure the CPU and RAM of the machine your task runs on |
|
|
| [Idempotency](/idempotency) | Protect against mutations happening twice. |
|
|
| [Replaying](/replaying) | You can replay a single task or many at once with a new version of your code. |
|
|
| [Notifications](/notifications) | Send realtime notifications from your task that you can subscribe to from your backend or frontend. |
|