Skip to content

Commit 48789f5

Browse files
committed
wording
1 parent e3fb301 commit 48789f5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

versioned_docs/version-2.0/how_to_guides/tracing/data_export.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ data offline in a tool such as BigQuery, Snowflake, RedShift, Jupyter Notebooks,
1313

1414
An export can be launched to target a specific LangSmith project and date range. Once a batch export is launched, our system will handle the orchestration and resilience of the export process.
1515
Please note that exporting your data may take some time depending on the size of your data. We also have a limit on how many of your exports can run at the same time.
16-
There is a also a limit of one day of runtime per export job.
16+
Bulk exports also have a runtime timeout of 24 hours.
1717

1818
## Destinations
1919

@@ -25,7 +25,7 @@ other systems. The data export will contain equivalent data fields as the [Run d
2525

2626
### Destinations - Providing a S3 bucket
2727

28-
To export LangSmith data, you will need to provide a S3 bucket where the data will be exported to.
28+
To export LangSmith data, you will need to provide an S3 bucket where the data will be exported to.
2929

3030
The following information is needed for the export:
3131

0 commit comments

Comments
 (0)