Inside Activate
Connectors
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