> ## Documentation Index
> Fetch the complete documentation index at: https://docs.argyle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ongoing Refresh

> Receive new payroll data from active connections.

After the initial delivery, an active payroll connection can continue providing new records, such as paystubs and payroll documents, at the user's direction.

<Note>
  This page applies to payroll Data API workflows. For an updated banking report, use [Re-verification](/verifications/re-verification).
</Note>

## Connection state

Ongoing refresh continues for as long as the connected payroll system allows the connection to remain active.

Some payroll systems require the user to reauthenticate periodically. Existing data remains available after a disconnection, but new records stop arriving until the user completes the required [reconnection](/workflows/reconnecting-accounts).

## Item support

Support and known constraints can vary by Item.

* In Console, select the Item in [Coverage](https://console.argyle.com/coverage).
* In the API, [retrieve the Item](/api-reference/items/retrieve-an-item) and inspect `known_limitations`.

<Frame>
  <img src="https://mintcdn.com/argyle/zs6lb-w1jQV9DVbr/images/overview/ongoing-refresh/1-refresh.png?fit=max&auto=format&n=zs6lb-w1jQV9DVbr&q=85&s=98396ad5770be43b8637ad239a63d56e" alt="Check ongoing refresh support in Console or the Items API." width="2840" height="1093" data-path="images/overview/ongoing-refresh/1-refresh.png" />
</Frame>

## Refresh frequency

The refresh schedule depends on the Item and how its payroll system publishes new information.

Use the Item's `features.data_retrieval.refresh_frequency` value for the current documented interval instead of assuming one schedule for every connected account.

## Monitor new data

Subscribe to the resource events your application uses:

* `.added` for newly available records.
* `.updated` when an existing record changes.
* `.removed` when the resource supports removal events.

Subscribe to the [`accounts.updated`](/api-reference/accounts-webhooks/updated) webhook to track account-status and synchronization changes. If the account enters an error state, inspect the current error code and follow [Reconnecting Accounts](/workflows/reconnecting-accounts).

## Simulate a refresh

Sandbox can simulate new data appearing after the initial connection. See [Simulate a data refresh](/overview/sandbox-testing#simulate-a-data-refresh).