Issues and Alerts

When Talk2sync encounters problems updating or inserting data, alerts, warnings, and notices appear for each product or order equivalence. Understanding these messages helps you quickly identify and resolve synchronization issues.

Alert Types

Alerts

Alerts are critical issues that prevent data synchronization. When an alert appears, the operation cannot proceed without resolution.

Common Alert Scenarios:

  • Validation errors from the external platform
  • Missing required fields
  • Authentication failures
  • API connection errors
  • Data format incompatibilities

Warnings

Warnings indicate non-critical issues that may affect synchronization or data quality, but don't necessarily prevent the operation.

Common Warning Scenarios:

  • Optional fields missing
  • Data formatting inconsistencies
  • Platform-specific limitations
  • Performance concerns

Notices

Notices are informational messages that don't block operations but provide useful context.

Common Notice Scenarios:

  • Operation completed with notes
  • Platform-specific responses
  • Partial updates completed
  • Additional context about the operation

Issue Bubbles

Each product or order equivalence can display information bubbles containing:

What Issue Bubbles Show

  • Error Messages - Specific descriptions of what went wrong
  • Validation Issues - Fields that failed validation
  • Platform Messages - Direct messages from the external platform
  • Reasons for Failure - Why the update or insert is not happening
  • Suggested Actions - How to resolve the issue

Reading Issue Messages

Issue messages typically include:

  1. Error Type - What kind of problem occurred
  2. Affected Field - Which data field has the issue
  3. Error Description - What the specific problem is
  4. Platform Response - The external platform's feedback (if available)
  5. Action Needed - What you need to do to fix it

Example Issue Messages

Validation Error:

Error: Price validation failed
Field: Product Price
Message: Price must be greater than 0
Action: Update the product price to a valid amount

Missing Required Field:

Warning: Missing required field
Field: Product Category
Message: Category is required for this platform
Action: Add a category to the product

Authentication Error:

Alert: Authentication failed
Field: API Credentials
Message: Invalid API key or expired credentials
Action: Re-authenticate in Settings

Notifications Popover Menu

Accessing Notifications

In the main navigation bar of the Talk2sync panel, there is a Notifications button (usually a bell icon) that opens a popover menu.

What the Notifications Menu Shows

  • List of Recent Issues - All alerts, warnings, and notices
  • Issue Count - Total number of active issues
  • Grouped by Type - Organized by alert level
  • Timestamps - When each issue occurred
  • Quick Actions - Direct links to affected records

Troubleshoot Button

Inside the Notifications popover menu, there is a Troubleshoot button that performs automated analysis.

Troubleshooting Analysis

What Troubleshoot Does

The Troubleshoot button triggers a comprehensive analysis of all issues in your account:

  1. Scans All Connections - Reviews all connected platforms
  2. Identifies All Issues - Finds every alert, warning, and notice
  3. Analyzes Patterns - Looks for recurring problem themes
  4. Detects Scale Issues - When the same error occurs many times
  5. Generates Report - Provides a structured analysis report

Pattern Detection

When there are many similar issues, the Troubleshoot analysis:

  • Groups Similar Errors - Combines the same error type across multiple records
  • Identifies Root Cause - Finds the common underlying problem
  • Shows Impact - Indicates how many records are affected
  • Suggests Solutions - Recommends fixes for the pattern

Example Pattern Analysis

Scenario: 150 products failing to sync

Without Pattern Detection: You see 150 individual error messages (overwhelming)

With Troubleshoot Analysis:

Pattern Identified: Missing Category Field
Affected Records: 150 products
Root Cause: Category field not mapped in connection settings
Solution: Configure category field mapping in Settings
Estimated Fix Time: 5 minutes to configure, 10 minutes to resync

Using Issue Information to Troubleshoot

Step-by-Step Process

  1. Check Notifications Menu - See what issues are present
  2. Click Troubleshoot - Run pattern analysis
  3. Review Analysis Report - Understand the patterns
  4. Identify Root Cause - What's causing the issues
  5. Apply Fix - Make necessary changes
  6. Resync Data - Send updates again
  7. Monitor Results - Verify issues are resolved

Common Issue Patterns

Pattern 1: Validation Errors

  • Issue: Multiple products failing price validation
  • Cause: Price field format or value issue
  • Fix: Update price format or validate values

Pattern 2: Missing Fields

  • Issue: Many products missing required fields
  • Cause: Field not mapped in connection settings
  • Fix: Configure field mapping

Pattern 3: Authentication Issues

  • Issue: All sync operations failing
  • Cause: API credentials expired or incorrect
  • Fix: Re-authenticate in Settings

Pattern 4: Format Incompatibility

  • Issue: Specific field type failing across records
  • Cause: Data format doesn't match platform requirements
  • Fix: Adjust field configuration or data transformation

Tackling Issues at Scale

When You Have Many Issues

Large-Scale Problem Approach:

  1. Run Troubleshoot Analysis - Identify the main patterns
  2. Find Root Cause - Usually 1-3 main issues cause most problems
  3. Fix the Root Cause - Solve the underlying problem
  4. Re-sync Everything - Send all updates at once
  5. Verify Results - Check if issues are resolved

Example: Fixing 1,000 Issues

Scenario: 1,000 orders failing to sync, showing different error messages

Analysis Step:

  • Run Troubleshoot
  • Discover all 1,000 errors stem from one mapping configuration

Fix Step:

  • Update the one configuration setting
  • Re-sync all 1,000 orders

Result:

  • All 1,000 orders sync successfully
  • Fixed 1,000 issues with one change

Bulk Issue Resolution

Instead of fixing each issue individually:

  1. Identify the Pattern - What's causing the errors
  2. Fix at the Source - Update settings, mappings, or configuration
  3. Apply to All - The fix applies to all affected records
  4. Batch Resync - Send all changes at once

Best Practices for Issue Management

✓ Do:

  • Check Notifications regularly
  • Use Troubleshoot to find patterns
  • Address root causes rather than individual issues
  • Test fixes with a small batch first
  • Document issues and their solutions
  • Keep issue tracking for reference
  • Resolve issues promptly to avoid data inconsistency

✗ Don't:

  • Ignore alerts and warnings
  • Try to send updates without resolving issues
  • Fix issues one-by-one without finding patterns
  • Assume errors will resolve themselves
  • Leave problematic data in the system
  • Ignore recurring issue patterns
  • Proceed without understanding error messages
Last Updated: