ZenotiHelp

Data freshness and scheduling

ZTZenoti Docs Team Updated April 10, 2026 2 min readGuide

Monitor and understand how Analytics β€” Amazon S3 delivers fresh data to your S3 bucket through automated refresh cycles.

Before you begin

  • Your organization must have an active Analytics β€” Amazon S3 subscription.
  • The initial onboarding and full data load must be complete.
  • You need access to your organization's S3 bucket to monitor data delivery.

Steps

Monitor data refresh cycles

Analytics β€” Amazon S3 automatically refreshes your data every 1–2 hours during normal operation. Each refresh creates a new GroupID folder in your S3 bucket containing the latest changes.

  1. Navigate to your S3 bucket and locate the PODName folder for your organization.
  2. Review the GroupID folders to see refresh history:
  • GroupID 1 β€” Contains your complete historical data from the initial full load.
  • GroupID 2, 3, 4... β€” Contains incremental changes from each refresh cycle.
  1. Check the timestamp on each GroupID folder to verify refresh frequency.

Note: Exact refresh timing depends on data volume and processing conditions. During high-volume periods, refreshes may take slightly longer than the standard 1–2 hour interval.

Use data freshness indicators

Each table in your S3 data includes timestamp columns that help you track data freshness:

  • EtlLastUpdatedOn β€” Shows when each record was last refreshed.
  • etlcreateddate β€” Shows when each record was first created in the data warehouse.

Use these columns to implement incremental sync in your BI tools:

SELECT *
FROM Bi_FactInvoiceItem
WHERE etlcreateddate > @LastSyncTimestamp
  AND void = 0;

Track monthly snapshots

If your organization has monthly snapshots enabled, the system creates point-in-time data preservation on the 1st of each month.

  1. Navigate to the MonthlySnapshot folder in your S3 bucket.
  2. Review the folder structure: MonthlySnapshot/ExtractDate/PodName/GroupID/FactName/.
  3. Monthly snapshot GroupIDs start at the 1000 series to distinguish them from regular incremental loads.

Important: Monthly snapshots are only available after all your centers are onboarded and historical data has been provided. The following tables are excluded from monthly snapshots: Bi_FactEmployeeMembershipCommissions, Bi_FactItemCommissionDeductions, Bi_FactMultipleEmployeeCommission, Bi_FactAdoptionSummary, Bi_FactOpportunityCustomFieldValues, Bi_DimUtcToCenterTime, Bi_FactCampaignSummary, Bi_FactEmployeeItemLevelCommissions.

Monitor processing status

During each refresh cycle, the system creates temporary processing folders to ensure data consistency:

  1. Look for folders named <groupid_processing> during active refresh cycles.
  2. When processing completes successfully, these folders are renamed to the final GroupID number.
  3. If a processing folder remains for an extended period, contact Zenoti Support as this may indicate a processing issue.

Handle large data volumes

For organizations with high transaction volumes, the system may split table data across multiple CSV files within each GroupID folder:

  • Data0.csv β€” First batch of records.
  • Data1.csv β€” Second batch of records.
  • Data2.csv β€” Additional batches as needed.

Configure your BI tools to process all CSV files within each table folder to ensure complete data coverage.

Tips

  • Set up monitoring alerts in your BI tools to detect when new GroupID folders appear in your S3 bucket.
  • Use the etlcreateddate column to identify the most recently refreshed records in each table.
  • For troubleshooting data freshness issues, compare the timestamp on your latest GroupID folder with your expected refresh schedule.
Was this article helpful?
Your feedback helps us improve our documentation.