# FAQs {% hint style="info" %} CONNECTORS ARE COMING AUGUST 2026 {% endhint %} This page answers the most common questions about Connectors. For troubleshooting failed runs, see Troubleshooting. For security and compliance questions, see Security and Data Handling. *** ### How often do Import Connectors run? Import Connectors scan configured storage locations automatically every five minutes. If a matching file is found, it is picked up and processed. No manual trigger is required. *** ### How often do Export Connectors run? Export Connectors run on a schedule you configure during setup. Available frequencies are every 10 minutes, hourly, daily, weekly, or monthly. *** ### Can I run a Connector manually? No. Connectors run automatically based on their configuration and cannot be triggered manually. Import Connectors scan configured storage locations every five minutes. If a matching file is present, it will be picked up and processed in the next scan cycle — so there is no need to trigger a run manually. Export Connectors run on the schedule you configured during setup, which can be set to every 10 minutes, hourly, daily, weekly, or monthly. If you need to change how often an Export Connector runs, update the schedule in the Connector settings. If you need to reprocess data outside of the normal cycle, upload a new file that matches the configured file pattern and it will be picked up at the next scan. *** ### Can I deactivate a Connector? Yes. Use the Active toggle in the Connectors dashboard to deactivate a Connector at any time. When inactive, the Connector will not run. Note that you cannot pause a Connector that is currently running. *** ### What happens if no matching file is found? If no file matches the configured file pattern, the Connector will not process anything. You can configure no-file notifications to alert your team if an expected file has not been received within a defined time threshold. *** ### What happens if a Connector fails? The run will show a status of **Failed** in the dashboard, and a failure notification will be sent to configured recipients. Open the Connector's run history to review the error message and identify the cause. See [Troubleshooting](/documentation/data-and-integrations/connectors/troubleshooting.md) for common failure scenarios. *** ### Can I change the file structure after a Connector is activated? Not without updating the Connector first. If you need to add, remove, or rename columns, update the Connector configuration before uploading a new file. Connectors expect a consistent file structure once activated. *** ### Does UbiQuity host my storage? No. Your organisation must host and manage its own SFTP server, Azure Blob container, or Amazon S3 bucket. UbiQuity connects securely to your environment but does not provision or manage storage on your behalf. *** ### How is billing handled? Connectors are billed monthly, per Connector. Billing begins when a Connector is activated and is charged for the full month — partial months are not prorated. If you deactivate a Connector during the month, the full monthly charge still applies for that billing period. See the [UbiQuity pricing page](https://www.ubiquity.co.nz/platform/connectors#pricing) for current pricing. *** ### Are Connectors secure? Yes. Connectors follow the same security and compliance standards as the wider UbiQuity platform. All data is encrypted in transit and at rest, access is permission-controlled, and all Connector activity is logged. UbiQuity is certified to ISO/IEC 27001:2022. See [Security and Data Handling](/documentation/data-and-integrations/connectors/security-and-data-handling.md) for full details. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ubiquity.co.nz/documentation/data-and-integrations/connectors/faqs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.