How extractions start
Extractions can start in several ways:| Trigger | When to use it |
|---|---|
| First-time extraction rules | Automatically retrieve the standard data your organization needs after an entity is created or onboarded |
| Manual update | Refresh a specific entity when your team needs newer information |
| Recurring scheduler | Keep selected entities updated on a schedule using tags |
| API request | Start an extraction from your own integration |
Extraction status
An extraction moves through statuses while Syntage queues, runs, and finishes the work. In the dashboard, check the status to understand whether Syntage is still retrieving data, waiting for a prerequisite, finished, or unable to complete the extraction.Waiting means Syntage cannot run the extraction yet because something still blocks it, such as missing entity information, authorization, an unavailable credential, or an internal dependency. If an extraction fails or remains pending longer than expected, check whether the datasource is available, whether the entity’s credential or authorization is valid, and whether the extraction reached a datasource limit.
For the exact API status values, billing behavior for stopped or cancelled extractions, and extraction error codes, see the Extractions resource guide.
Extractions, reports, and data
Extractions retrieve source information. Syntage then uses that information to populate:- Reports, where your team reviews processed indicators, summaries, charts, and analysis
- Data, where your team reviews source records, raw structured data, and original files
- Exports, where your team downloads information that Syntage already retrieved