Operational guidance for running installed connectors — how often they poll, how to find their schedules, how to monitor health, and how to recover when something drifts. For what each connector actually does, see Capabilities.
Polling cadence#
When installing a connector — on Formance Console or via the API — you can configure a pollingPeriod that defaults to 30 minutes if not specified. It drives every periodic capability the connector exposes — Accounts, Balances, External Accounts, Payments, Orders, Conversions, plus the poll loop on in-flight Transfer / Payout statuses.
Each connector declares a minimum polling period the platform enforces at install time. The common floor is 20 minutes (Stripe, Bankingcircle, Routable, Bitstamp, Mangopay, …); a few connectors with slower-moving data or stricter upstream rate limits raise the floor higher. Submitting a pollingPeriod below the floor is rejected with a clear validation error before the connector is installed — see the per-connector page for the exact value (look for the pollingPeriod row in the Configuration fields table).
Monitoring connector schedules#
To check when a connector last pulled data, use the Connector Schedule APIs.
Finding the schedule ID#
Each connector has schedules that are automatically generated when the connector is installed. The schedule ID follows this format:
{stackID}-{connectorID}-{capability}For example: stack123-abc-FETCH_ACCOUNTS
To find the schedule IDs for your connectors, use the List All Connector Schedules endpoint.
Checking last pull time#
Once you have the schedule ID, call the List Connector Schedule Instances endpoint with the schedule ID to see the history of data pulls, including the most recent one.
This is useful for:
- Debugging synchronization issues
- Monitoring connector health
- Verifying data freshness