Skip to content

Commit 24c7342

Browse files
committed
Edits
1 parent 2827de1 commit 24c7342

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/engage/audiences/sql-traits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -243,6 +243,6 @@ You might be returning a value for `user_id` that's inconsistent with how you tr
243243

244244
If you see only question marks in the preview, and have already tracked data historically with Segment, then you likely have the wrong column. If your cloud source doesn't have the database `user_id`, Segment recommends using a `JOIN` clause with an internal users table before sending the results back to Segment.
245245

246-
### Why some SQL trait’s settings do not have the “Compute Schedule” option?
246+
### Why do some SQL Trait settings not have the “Compute schedule” option?
247247

248-
The compute schedule feature was added on Feb 8,2021, so traits created prior to this date will not have this option available. If your trait lacks this feature, recreating it will make it available.
248+
Segment added the compute schedule feature on Feb 8, 2021, so traits created prior to this date will not have this option. If your trait lacks this feature, recreating it will make it available.

0 commit comments

Comments
 (0)