Monitoring & Troubleshooting
5 min
Effective monitoring and quick response reduce downtime and data drift across systems. This section outlines operational checks and troubleshooting practices for connectors.
Routine Monitoring
- Connector Dashboard: Review recent runs, success counts, and error summaries.
- Change Volumes: Track number of creates, updates, deletes per run for anomalies.
- Notifications: Set up notify actions on errors or thresholds.
- Scheduled Runs: Confirm job frequency matches data freshness requirements.
Common Operational Checks
Area | What to Check | Resolution |
|---|---|---|
Import Stage | File or query availability | Confirm source accessibility and permissions |
ProcessImport | maxChanges or maxDelete exceeded | Review source data; reset thresholds if safe |
Process Stage | Change handler errors | Check handler configuration and linked resources |
Database | Table locks or missing schema | Verify schema alignment and table existence |
Scripts | Script errors or missing resources | Confirm resource path and syntax |
Reviewing Logs
- Use Activate Server logs (\ProgramData\Activate\Logs) for import or script exceptions.
- Check Connector History Table for processed row counts and timestamps.
- In the Connector Data Table, look for rows marked as Error or Retry.
SELECT * FROM [Connector_DataTable] WHERE Action = 'Error'
Error Recovery
- Correct the underlying issue (e.g., schema mismatch, missing data).
- Rerun the connector workflow manually.
- If the issue persists, clear error flags only after root cause is identified.
<options>
<retry>
<clear>true</clear>
</retry>
</options>
Preventive Practices
- Keep import source definitions versioned (SQL views, scripts, etc.).
- Document and review thresholds (maxDelete, maxChanges) quarterly.
- Periodically prune old history table records to maintain performance.
- Validate connector scheduling after system upgrades.