Monitoring Connectors
How to track Connector activity, review run history, and set up notifications.
Overview
Once a Connector is active, it runs automatically. You can monitor activity in three ways: the Connectors dashboard, individual Connector run history, and email notifications. Together these give you visibility into whether your data is being imported or exported as expected.
Connectors dashboard
The Connectors dashboard provides a high-level view of all configured Connectors.
📸 Screenshot of the Connectors dashboard
For each Connector, the dashboard shows:
Connector name
The name assigned during setup
Database
The UbiQuity database the Connector is associated with
Direction
Whether the Connector is importing or exporting
Source / Destination
The storage type (SFTP, Azure Blob Storage, or Amazon S3)
Last run time
When the Connector last ran
Last status
The outcome of the most recent run
Active status
Whether the Connector is currently active
Connector statuses
Each run displays one of the following statuses:
Running
The Connector is currently processing a file
Completed
The run finished successfully. For imports, data has been written to UbiQuity
Failed
The Connector encountered an error and did not complete
If a run shows Failed, select the Connector to open its run history and review the error details. See Troubleshooting for guidance on common errors.
Run history
Selecting a Connector from the dashboard opens its run history. The run history shows:
Run name
Status
Start time
End time
Duration
You can expand an individual run to see additional detail, including a summary of what was imported or exported during that run.
📸 Screenshot of a Connector run history
Email notifications
Connectors can send email notifications to recipients you configure during setup. Notifications provide visibility without needing to log in to UbiQuity.
Success notifications
A success email is sent after a Connector completes successfully. For imports, this includes:
File name processed
Total rows processed
Rows inserted
Rows updated
Rows failed
Rows skipped
Failure notifications
If a Connector run fails, a failure notification is sent to configured recipients. The email includes the Connector name, the file involved where applicable, and a summary of the failure.
No-file notifications
You can configure no-file notifications to alert your team if an expected file has not been received within a defined time threshold. This helps catch missing data feeds before they affect campaigns or reporting.
What to do if a Connector fails
If a run shows as Failed:
Open the Connector's run history and review the error message
Confirm the file matches the configured file pattern
Verify credentials and permissions are still valid
Ensure the file was fully uploaded before the next scan cycle
If the issue persists, contact support with your account name, Connector name, run time, error message, and file name. See Troubleshooting for a full list of common errors and how to resolve them.
Last updated
Was this helpful?