LogoLogo
Home
  • Verb Documentation
  • Release Notes
  • Environment Settings
    • Authentication
      • Authentication Endpoint
  • Data Sources
    • Ingestion Methods
    • Table Sync Intervals
    • Data Source Integrations
      • Network Permissions
      • Microsoft SQL Server
      • PostgreSQL
      • MongoDB
      • Snowflake
      • Elasticsearch
      • DynamoDB
      • Google BigQuery
      • Firebase Cloud Firestore
      • Supabase
      • Cloud Files
      • Flat Files
    • Data Synchronization
      • Synchronization Methods
        • Full Synchronization
        • Incremental Synchronization
        • Change Tracking
        • Change Data Capture
      • Synchronization Intervals
      • Synchronization Status
        • Pausing and Resuming
      • Synchronization History
      • Schema Changes
      • Row Filtering
      • Schemaless & NoSQL
      • Managing Connections
      • Troubleshooting
  • Models
    • What is a Model
      • Elements of a Model
      • Model Management
    • Building a Model
      • Add/Remove Data
      • Relationships
      • Row-Level Security
      • Transformations
    • Advanced Model Information
      • Database Keys
      • Unstructured Data
      • Publishing Updates
      • Troubleshooting
      • Automatic Modeling
  • Data Transformations
    • What is a Transformation
      • Elements of a Transformation
      • Transformation Management
    • Building Transformations
      • Creating Transformations
      • Configure Transformation Steps
      • Transformation Steps
        • Calculator
        • Manipulate Text
        • Map Values
        • Remove Duplicates
        • Date Operation
        • Select Columns
        • Change Type
        • Group Data
        • Filter Data
        • Join Data
        • Append Rows
        • Pivot Data
        • Rank Data
        • Window Data
      • Complete and Publish
  • Collections
    • What is a Collection
      • Elements of a Collection
    • Building Collections
    • API Collections
      • Building API Collections
        • Connect Data Sources
        • Data Model
        • Select Data
        • Authentication and Security
        • Data Access API Keys
        • Data Access API Documentation
      • API Collection Versions
    • Advanced Collection Options
      • Time Zones
      • Currency Symbols
  • Tiles
    • What is a Tile
      • Elements of a Tile
    • Tile Management
      • Tile Data
    • Tile Actions
    • Custom Date Formats
    • Currency Conversion
  • Design Themes
    • What is a Design Theme
    • General Theme Settings
    • Data Visualization Settings
  • Account Settings
    • Integrations
      • Slack
  • Legal
    • Terms of Use
    • Privacy Policy
    • Subscription Agreement Terms
    • Subscription Agreement
    • Data Processing Addendum
Powered by GitBook
On this page

Was this helpful?

  1. Data Sources
  2. Data Synchronization

Synchronization History

Tracking the interaction history of your data source

PreviousPausing and ResumingNextSchema Changes

Last updated 2 years ago

Was this helpful?

Verb keeps a rolling 30 day audit log of all the interactions with your data source. Each time our system connects to a database or reads from a cloud-hosted file, our system logs the success or failure of that interaction. If you're data source is configured to synchronize data every hour, then your data source will have 24 historical log entries per day. These entries are a sign of the overall health of the data synchronization process.

When errors occur, Verb will attempt to handle the issue and fall back gracefully. For example, if one table cannot be read (for example due to column changes), the remainder of the tables will still be queried. You can follow our to diagnose and fix any issues that occur.

Clicking any object (table) in your data source will show the last 24 hours of synchronization history by default. You can view previous synchronizations day by day.

The 30 day view gives a broader picture of the success over time and can help to identify periodic failures that may arise.

troubleshooting steps