_Docs/
Get StartedModulesPlatformDeployCookbookChangelogReference
_Stack
_Modules
  • Ledger
  • Numscript
  • Connectivity
    • Capabilities
    • Operations
    • Accounts
    • Payments
    • Transfer Initiation
    • Account Pools
    • Payment Service Users
    • Connectors
      • Generic ConnectorEE
        • Getting Started
        • How it Works
      • PSP Connectors
        • Adyen
        • Atlar
        • Bankingcircle
        • Column
        • Currencycloud
        • Increase
        • Mangopay
        • Modulr
        • Moneycorp
        • Qonto
        • Stripe
        • Wise
        • Banking BridgeEE
        • RoutableEE
      • Exchange Connectors
        • Coinbase PrimeEE
          • Payments
          • Conversions
          • Orders
        • FireblocksEE
        • BitstampEE
      • Open BankingEE
        • Getting Started with Open Banking
        • Plaid
        • Tink
        • Powens
      • Build a connector
  • WalletsEE
  • FlowsEE
  • ReconciliationEE
  1. Modules
  2. Connectivity
  3. Operations
Connectivity

Operations

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 polling period that defaults to 30 minutes if not specified.

This polling period is used to periodically poll the payment service provider in order to fetch all the data the platform needs: Payments, Accounts, Transfer / Payout statuses, and any other capability the connector exposes.

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
CapabilitiesAccounts
On This Page
  • Polling cadence
  • Monitoring connector schedules
  • Finding the schedule ID
  • Checking last pull time