@@ -75,7 +75,7 @@ The default API URL is `https://api.trigger.dev`.
 
 ## Access presets
 
-Access presets define what a key can do. Some presets require a paid plan. The dashboard shows which presets your organization can use — see [pricing](https://trigger.dev/pricing).
+Access presets define what a key can do. On the Free and Hobby plans only the **No restrictions** preset is available. All other presets require the Pro or Enterprise plan.
 
 | Preset | Access |
 | --- | --- |
@@ -87,7 +87,7 @@ Access presets define what a key can do. Some presets require a paid plan. The d
 | **Variables only** | Read and write environment variables in this environment |
 | **No restrictions** | Full access to the environment |
 
-**Trigger only** and **Task operator** can be restricted to selected tasks. Task restrictions use task identifiers, such as `send-email`. A request involving multiple tasks — such as a batch trigger — succeeds only when the key can access every task in the request, so a task-restricted key can batch-trigger only its selected tasks.
+**Trigger only** and **Task operator** can be restricted to selected tasks, up to 10 tasks per key. Task restrictions use task identifiers, such as `send-email`. A request involving multiple tasks — such as a batch trigger — succeeds only when the key can access every task in the request, so a task-restricted key can batch-trigger only its selected tasks.
 
 ## Deploy with an API key
 
@@ -124,7 +124,7 @@ Use `@trigger.dev/sdk` version 4.5.8 or later to create public tokens with envir
 
 - The token must request at least one scope.
 - Its scopes cannot exceed the key's access.
-- Its expiration cannot exceed 30 days.
+- Its expiration cannot exceed 30 days (the default is 15 minutes).
 
 <Note>
 Revoking or expiring an API key does not revoke tokens it already created. Those tokens remain valid until their own expiration.
 
@@ -49,7 +49,7 @@ When your organization's spend reaches the billing limit, billable environments
 2. New runs can still be triggered and are queued, but they won't start executing. Queued runs incur no compute cost until they start.
 3. You have **24 hours** to review and decide what to do.
 
-If you don't act before the grace period ends, queued runs are canceled and new triggers are rejected for the rest of the billing cycle.
+If you don't act before the grace period ends, new triggers are rejected until you increase or remove the limit (limits also reset at the start of each billing cycle). Queued runs stay queued until you resolve the limit and choose to resume or cancel them. If the limit is still in place when a new billing cycle starts, queued runs resume automatically. Runs that have a TTL still expire if they stay queued past it.
 
 <Note>
   Billing limits are **soft limits**, not instantaneous hard caps. Usage is evaluated on a short
 
@@ -59,7 +59,7 @@ You can also set the branch with the `TRIGGER_DEV_BRANCH` environment variable i
 
 ## Archive a branch
 
-Archive a branch from the CLI when you no longer need it. The CLI detects your local git branch, or you can name one with `--branch`:
+Archive a branch from the CLI when you no longer need it. Pass the branch with `--branch` (or set `TRIGGER_DEV_BRANCH`); it's required, and the `default` branch can't be archived:
 
 <CodeGroup>
 
@@ -81,12 +81,12 @@ You can also create and archive branches from the **Dev branches** page in the d
 
 ## Limits on active branches
 
-Each branch has its own concurrency, so we limit how many can be active per project. Archive a branch at any time to unlock another slot.
+Each branch has its own concurrency, so we limit how many dev branches each developer can have active per project. The `default` development environment counts toward this limit. If you are at the limit when you run `dev --branch`, the CLI automatically archives up to 3 of your branches that have no connected dev session and have been idle for over an hour, to make room. You can also archive a branch any time to free a slot.
 
 | Plan  | Active dev branches |
 | ----- | ------------------- |
-| Free  | 25                  |
-| Hobby | 25                  |
-| Pro   | 25                  |
+| Free  | 50                  |
+| Hobby | 50                  |
+| Pro   | 50                  |
 
 Need more? [Get in touch](https://trigger.dev/contact) and we'll raise the limit.
@@ -124,8 +124,6 @@ Payloads and outputs over 512KB are kept in object storage rather than inline. C
 
 A single batch can have a maximum of 1,000 items with SDK 4.3.1+. Prior versions are limited to 500 items.
 
-<SoftLimit />
-
 ## Batch trigger rate limits
 
 Batch triggering uses a token bucket algorithm to rate limit the number of runs you can trigger per environment. Each run in a batch consumes one token.
@@ -170,8 +168,8 @@ We limit the size of logs to prevent oversized data potentially causing issues.
 
 #### Attribute Limits
 
-- Span Attribute Count Limit: 256
-- Log Attribute Count Limit: 256
+- Span Attribute Count Limit: 1024
+- Log Attribute Count Limit: 1024
 - Span Attribute Value Length Limit: 131072 characters
 - Log Attribute Value Length Limit: 131072 characters
 
@@ -188,8 +186,8 @@ We limit the size of logs to prevent oversized data potentially causing issues.
 
 #### Attribute Clipping Behavior
 
-- Attributes exceeding the value length limit (1028 characters) are discarded.
-- If the total number of attributes exceeds 256, additional attributes are not included.
+- Attributes exceeding the value length limit (131072 characters) are discarded.
+- If the total number of attributes exceeds 1024, additional attributes are not included.
 
 #### Attribute Value Size Calculation
 
 
@@ -98,5 +98,7 @@ There is a separate concurrency limits for metric widgets.
 | Limit                     | Details        |
 | :------------------------ | :------------- |
 | Concurrent widget queries | 30 per project |
+| Custom dashboards         | Free 0, Hobby 1, Pro 5 per organization |
+| Widgets per dashboard     | Free 0, Hobby 10, Pro 20 |
 
 See [Limits](/limits) for details.