Skip to content

Commit b35378c

Browse files
authored
Update linked-audiences.md
1 parent 08a06de commit b35378c

File tree

1 file changed

+3
-22
lines changed

1 file changed

+3
-22
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 3 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -54,28 +54,9 @@ As you're building your Linked Audience, you can choose from the following condi
5454

5555
#### Error States
5656

57-
As you’re building or maintaining your audience, you may encounter an error or warning message about possible impacts to your audience. Below are some common reasons errors occur, along with suggested troubleshooting steps.
58-
59-
| Failure | External message | Workflow implication |
60-
|---|---|---|
61-
| Parse error | An unknown error occurred. Execution will retry. If the problem persists, please contact Segment support. | Terminate and execute next run |
62-
| Graph missing entity | Entity missing from Data Graph: <entity> | Terminate and execute next run |
63-
| Graph missing column for entity | Entity column missing from Data Graph for Entity <entity> and Column: <column> | Terminate and execute next run |
64-
| No columns exist for entity | No columns exist for entity in Data Graph: <entity> | Terminate and execute next run |
65-
| Missing join key between entities | Join key missing from Data Graph for relation: <relationship> | Terminate and execute next run |
66-
| Join key is wrong type | Relationship key should be a string: <relationship> | Terminate and execute next run |
67-
| Entity relationship not in Data Graph | Entity relationship not in Data Graph for entity <entity> | Terminate and execute next run |
68-
| Entity relationship not in Data Graph | Entity relationship not in Data Graph for relationship: <relationship slug> | Terminate and execute next run |
69-
| Entity relationship not in Data Graph | Entity relationship not in Data Graph for entity: <entity> and relationship: <relationship slug> | Terminate and execute next run |
70-
| Query fails for unknown internal error | An unexpected error occurred. Execution will retry. If the problem persists, please contact Segment support. | Retry |
71-
| Update model fails | An unexpected error occurred. Execution will retry. If the problem persists, please contact Segment support. | Retry |
72-
| Kick off rETL job | An unexpected error occurred. Execution will retry. If the problem persists, please contact Segment support. | Retry |
73-
| Warehouse errors | Pass through warehouse errors | Terminate and execute next run |
74-
| SQL Compilation execution | Examples: extract phase failed: An unexpected Snowflake error occurred trying to execute your model query: 000904 (42000): SQL compilation error: error line 30 at position 61 invalid identifier '<XX.PROPERTIES>' extract phase failed: An unexpected Snowflake error occurred trying to execute your model query: 000904 (42000): SQL compilation error: error line 23 at position 19 invalid identifier '<XX.TRAITS>' | |
75-
| Duplicate records for ID | Examples: extract phase failed: Duplicate records have been detected. This could be because the model query returned multiple records for the same ID column (MATCHID), or the Segment records table itself has duplicate records. | |
76-
| Check results | An unexpected error occurred attempting to execute this model query. | Retry |
77-
| Process results | Execution is paused due to an identified operational issue. | Pause for manual intervention |
78-
| Load results | Execution is paused due to an identified operational issue. | |
57+
As you’re building or maintaining your audience, you may encounter errors or warning messages about possible issues with your audience. For example, when Segment tries to compute your audience, and an entity or entity column from your linked audience definition is missing from your data graph or data warehouse, then you may see an error on the linked audiences overview page in Segment. Additionally, computing your linked audineces is a multi-step process, and sometimes an error can occur in one of the steps of the workflow.
58+
59+
Generally, when an error occurs, Segment will retry that step or Segment will terminate the workflow and try to re-run it again at the next scheduled compute run. If you need more help diagnosing your errors or warnings, reach out to [[email protected]](mailto:[email protected]){:target="_blank"}.
7960

8061
#### Edit an audience
8162
To edit an audience:

0 commit comments

Comments
 (0)