Skip to main content

Event Data Sync Issues in Vitally

Errors syncing event data from Snowflake to Vitally due to timestamp filtering, missing required fields, or duplicate account ID columns.

Cassie avatar
Written by Cassie
Updated this week

Problem Description:

Users may encounter issues when pulling event data from Snowflake into Vitally. While the sample query runs successfully, data may not appear in Vitally, even after attempting to create a custom object.

Potential Reasons for the Issue:

  1. Incremental Sync Constraints:

    • If the sync has never been run before, there might be no initial reference timestamp.

  2. Incorrect Filtering Conditions:

    • Filtering with $LAST_SYNC_TIMESTAMP may cause events to be excluded.

    • If the WHERE clause is removed but data still doesn’t appear, additional constraints might be affecting the query.

  3. Missing Required Fields:

    • Custom objects require specific columns:

      • timestamp for event occurrence time.

      • object_id as a unique identifier.

      • external_account_ids or external_organization_ids to associate with an account or organization.

      • name to label the object.

    • If any of these fields are empty or unmapped, Vitally may fail to sync them.

  4. Unexpected Sync Errors:

    • Errors displayed in the UI could indicate that required fields are not properly mapped under Accounts, Users, Events, or Custom Objects.

  5. Duplicate Account ID Columns:

    • Having multiple account ID columns in the dataset may cause sync failures.

Step-by-Step Solutions:

1. Verify Timestamp Conditions

  • Check the event created date in Snowflake.

  • Ensure the filtering conditions are met if any are set.

  • If the object has never been synced before, try removing the $LAST_SYNC_TIMESTAMP filter and rerun the sync.

2. Review Required Fields for Custom Objects

  • Ensure the following fields are included in the query:

    • timestamp

    • object_id

    • external_account_ids or external_organization_ids

    • name

  • Map all required fields in the Vitally interface.

3. Investigate UI Errors

  • If an error appears at the top of the screen, check if any required fields remain unmapped in:

    • Accounts

    • Users

    • Events

    • Custom Objects

  • Ensure no empty fields exist in these categories.

4. Check for Duplicate Columns

  • Look for duplicate Account ID columns in the dataset.

  • Ensure only one external_account_ids field is present.

5. Re-run the Sync

  • After making necessary adjustments, run the sync again.

  • Verify if events and custom objects now appear in Vitally.

Additional Tips:

  • Reference Vitally Documentation:

  • Check Sync Logs:

    • Use Vitally’s sync logs to determine if records were processed successfully.

  • Test with a Smaller Dataset:

    • Run queries with a limited dataset to isolate potential issues.

FAQs:

Q: My data is not appearing in Vitally. What should I check first?

A: Verify that the filters conditions are being met. If syncing for the first time, remove the timestamp filter.

Q: Why are some events missing in Vitally?

A: Check if all required fields (timestamp, object_id, external_account_ids, name) are present and mapped correctly.

Q: What does the sync error at the top of the screen mean?

A: It likely indicates missing required fields. Review field mappings in Accounts, Users, Events, or Custom Objects.

Q: My custom object sync is failing. What could be the issue?

A: Ensure that all required fields are correctly defined and that there are no duplicate Account ID columns.

Q: How can I confirm if my sync worked?

A: Check Vitally’s sync logs to see if events and custom objects were successfully imported.

Related Articles
Sync: Product Events
S3
Snowflake
Syncing Custom Objects
Syncing Events
Did this answer your question?