LangSmith adds organization limits to bulk exports across workspaces

LangSmith’s Cloud release notes for October 19–26 add default bulk‑export limits across all workspaces in an organization: 1,000 export creations per hour and 1,000 active schedules. The organization layer applies alongside existing workspace limits, so a request that fits one workspace’s budget can still encounter an organization‑wide limit.

The bulk‑export guide documents a workspace allowance of 250 export creations in a rolling 60‑minute window and 200 active recurring schedules. These are creation and schedule counts, rather than guarantees about how many exports finish or how much trace data can be transferred.

Documented default LangSmith Cloud limits

Scope	Export creations	Active schedules
Organization	1,000 per hour	1,000
Workspace	250 per rolling 60 minutes	200

The organization notes specify “per hour”; they do not describe that layer’s precise window algorithm. The rolling‑window detail is explicit for the workspace limit.

The [new organization rule](https://changelog.langchain.com/) excludes exports that existing schedules create automatically from its hourly creation total. The [workspace guide](https://docs.langchain.com/langsmith/data‑export), however, explicitly includes both one‑off exports and exports spawned by scheduled bulk exports in the workspace’s 250‑per‑hour budget. That distinction matters when several teams schedule recurring exports. Automatic runs can consume part of a workspace’s hourly creation allowance while being excluded from the organization’s hourly counter. The organization exemption therefore does not remove the documented workspace limit. Teams need to account for schedule‑generated work at the workspace level as well as new creation requests across the organization.

When an organization exceeds a limit, the changelog says create_bulk_export returns a 429 response. For the organization’s hourly limit, that response includes a Retry‑After header. The workspace guide separately says hourly‑limit rejections continue until earlier creations age out of its rolling 60‑minute window.

An active‑schedule cap measures configurations that remain active, rather than how often they have run. The workspace documentation explains that a recurring schedule still counts as one even after producing thousands of historical runs. One‑off exports do not consume that active‑schedule allocation.

At the workspace’s 200‑schedule limit, the guide says new scheduled requests receive a 429 until an existing schedule is cancelled. Waiting for an hourly window to pass does not itself remove an active schedule. The same guide also warns that cancelling a source schedule does not cancel exports it has already spawned; those jobs must be handled separately.

The current bulk‑export guide makes access dependent on signup date. Customers who signed up after August 3, 2026 need the LangSmith Enterprise plan for bulk export. Customers who signed up on or before August 3 can use it on Plus or Enterprise until February 1, 2027. A plan name alone therefore does not establish eligibility without the signup cohort.

The new organization announcement is specifically for LangSmith Cloud. The guide says self‑hosted LangSmith does not enforce the documented workspace creation and schedule limits by default; the Cloud announcement should not be treated as a universal self‑hosted configuration change.

After a creation request succeeds, its export still needs to complete. The guide distinguishes CREATED, RUNNING, COMPLETED, FAILED, CANCELLED and TIMEDOUT states, and says the Parquet files are available in the destination bucket once the status is COMPLETED. A request accepted within these limits is a job submission, not evidence of a finished export.

Conceptual illustration of separate organization and workspace export budgets, created for OpenTools. This is not a LangSmith interface or a measured result.