Overview
Time History tracks the "last loaded" date for each data type and direction in your integration. This date determines where the next sync starts — Junipeer only syncs records that have been created or modified after the last loaded date.
You can find the Time History page in the left sidebar of any integration.
How it works
Each row on the Time History page represents a specific data type and direction, for example:
Orders (e-commerce → ERP): last loaded 2026-03-24 14:30
Products (ERP → e-commerce): last loaded 2026-03-25 08:00
When a scheduled sync or webhook triggers a flow, Junipeer fetches records from the source platform that have been created or modified since the "last loaded" date. After the sync completes, the last loaded date is updated to the current time.
If no syncs have ever run for a data type, there will be no date shown, and the next sync will attempt to fetch all available records from the beginning.
Changing the last loaded date
Each row has a Change button that lets you manually adjust the last loaded date. This is useful in several scenarios:
Re-syncing after a fix
If you discovered and fixed a configuration issue (like a missing payment method mapping), you can move the last loaded date back to before the error occurred. The next sync will then re-process all records from that date forward.
Backfilling historical data
If you want to sync orders or products that were created before the integration was set up, move the last loaded date back to the desired start date. For example, setting the date to three months ago will cause the next sync to fetch all records from the past three months.
Resetting a drifted date
In rare cases, the last loaded date can drift due to interrupted syncs or system issues. If you notice that recent records are not being picked up, check whether the last loaded date is stuck at an old timestamp and update it to the correct value.
Important considerations
Moving the date backward will cause records to be re-synced. Records that already have References will be updated in the target platform rather than duplicated. Records without references will be created as new.
Moving the date forward will skip records between the old and new date. Those records will not be synced unless you move the date back again.
Large backfills can take time. If you move the date back significantly (e.g., a full year), the resulting sync may process thousands of records. Consider doing this during off-peak hours.
Date vs. order exclusion
The Time History date and the "Exclude orders created before this date" setting in Configure > Settings serve different purposes:
Time History controls the starting point for the next sync. It moves forward automatically as syncs complete.
Order exclusion date is a permanent filter. Orders created before that date are always excluded, even if you move the Time History date back past it.
Use the order exclusion date when you definitively do not want to sync old orders. Use Time History when you temporarily need to re-process a date range.
Tips
Always check Time History after resolving sync errors to ensure the date has not been left at an unexpected value.
When backfilling historical data, start with a small date range (e.g., one week) to verify the results before moving to a larger range.
The Time History page is per-flow, so you can adjust dates independently for orders, products, customers, etc.
If you are unsure whether records in a specific date range have been synced, check the Entities page to see which records Junipeer knows about.