Manage Skyvia Integration Queue Times Effectively

Tips for Managing Integration Queue Times

Overview

When an integration is triggered - either on schedule or manually - it is placed in an execution queue before record processing begins. Queue wait times are normal and typically last only a few seconds. However, during peak load periods, wait times may increase significantly.

Why Integrations Get Queued

Skyvia processes integrations concurrently across all accounts. Queue delays most commonly occur:

  • At the start of every hour (e.g., 11:00, 12:00, 13:00), when the largest number of scheduled integrations are triggered simultaneously
  • During periods of unusually high platform load

Queue Priority by Plan

Integrations on paid plans are processed with higher priority than Free plan integrations.

Tips to Minimize Queue Wait Time

  1. Avoid scheduling at the top of the hour. Instead of 12:00, schedule at 12:10 or 12:15. This distributes the load more evenly and reduces the chance of your integration waiting in a large queue.
  2. Upgrade to a paid plan. Paid plan integrations have higher queue priority and are processed before Free plan integrations.
  3. Stagger multiple integrations. If you run several integrations, avoid triggering them all at the same time. Schedule them a few minutes apart.

Still Experiencing Long Queue Times?

If your integration consistently waits more than a few minutes before processing begins, please contact Skyvia Support with the integration name and run timestamps so we can investigate.

    • Related Articles

    • Integration Failure Types in Skyvia Data Integration

      When using Skyvia Data Integration product, you may encounter two distinct types of integration failures: 1. Record-Level Errors These occur when one or more individual records fail to process during an integration task. For example, in operations ...

    • Data Integration: You have reached the limit of records

      The error "You have reached the limit of records" usually occurs when the number of records exceeds the limit specified in your current Data Integration product plan. To resolve this issue, you have a few options: Upgrade your plan to increase the ...

    • Skyvia Full (Initial) Replication

      Full Replication creates a complete copy of your source data in the target database. Use it for the first replication run, after schema changes, when refreshing all data, or if you encounter duplicate records. Requirements Valid Source and Target ...

    • Email Notifications for Integration Execution in Skyvia

      Overview Skyvia does not currently provide notifications for successful integration completion. However, you can configure email notifications to be alerted when an integration fails or when specific usage thresholds are reached. Notifications are ...

    • Understanding Records in Skyvia Data Integration

      What Is a Record? A record in Skyvia Data Integration represents a single row in a database table or a single object in a cloud source (e.g., one contact in Salesforce, one row in a Google Sheet). Every integration operation - Import, Export, ...