Skip to content

Commit 7ac39c4

Browse files
authored
Merge pull request #154 from segmentio/repo-sync
repo sync
2 parents 61a4e77 + 1f92477 commit 7ac39c4

File tree

2 files changed

+2
-5
lines changed

2 files changed

+2
-5
lines changed

src/connections/spec/common.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -302,10 +302,10 @@ Sending data to the rest of our destinations is opt-out so if you don't specify
302302

303303
Every API call has four timestamps, `originalTimestamp`, `timestamp`, `sentAt` and `receivedAt.` They're used for very different purposes.
304304

305-
**All timestamps are [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601) date strings.**
305+
**All timestamps are [ISO-8601](http://en.wikipedia.org/wiki/ISO_8601){:target="_blank"} date strings.**
306306

307307
> note ""
308-
> **NOTE:** ISO-8601 date strings with timezones included are required when using timestamps with [Personas](/docs/personas/). Sending custom traits without a timezone included in the timestamp will result in the value not being saved.
308+
> **NOTE:** You must use ISO-8601 date strings that include timezones when you use timestamps with [Personas](/docs/personas/). If you send custom traits without a timezone, Segment doesn't save the timestamp value.
309309
310310
### Timestamp Overview
311311

src/connections/storage/data-lakes/sync-history.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,6 @@ title: Data Lakes Sync History and Health
55

66
The Segment Data Lakes sync history and health tabs generate real-time information about data syncs so you can monitor the health and performance of your data lakes. These tools provide monitoring and debugging capabilities within the Data Lakes UI, so you can identify and proactively address data sync or data pipeline failures.
77

8-
> info ""
9-
> This feature is currently in Public Beta. Segment’s [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/) govern the use of this feature.
10-
118
## Sync History
129
The 'Sync History' table shows detailed information about the latest 100 syncs to the data lake. The table includes the following fields:
1310
* **Sync status:** The status of the sync: either 'Success,' indicating that all rows synced correctly, 'Partial Success,' indicating that some rows synced correctly, or 'Failed,' indicating that no rows synced correctly

0 commit comments

Comments
 (0)