Skip to main content

Troubleshooting Integration Timeouts

  • Updated

Overview

Integration timeouts occur when a connection between TrackVia and an external system takes longer than the allowed limit to respond. Workato enforces a 60-second timeout on all HTTP requests, including calls to the TrackVia API. When that limit is exceeded, the recipe job fails and Workato logs a timeout error.

This article explains the four most common causes of integration timeouts and provides step-by-step guidance for resolving each one.

Jump to Section

Common Causes of Timeouts

Timeouts in TrackVia integrations typically fall into one of four categories. The sections below describe each cause and how to address it.

To identify which cause applies to your situation, start by reviewing the job error in Workato:

  1. Open your recipe in Workato and navigate to the Jobs tab.
  2. Click the failed job to view its details.
  3. Expand the failed step to read the full error message. Timeout errors typically appear as: 408 Request Timeout, 504 Gateway Timeout, or MULE:RETRY_EXHAUSTED.
  4. Note which action step triggered the error — this will help you match the failure to one of the causes below.
⚠ Note on MULE:RETRY_EXHAUSTED: This error means Workato attempted the action multiple times and the request timed out on every retry. It does not indicate a Workato configuration error — it means the underlying request is consistently too slow to complete within the 60-second limit. Address the root cause using the steps below.

Cause 1: Large Data Payloads

Requests that retrieve or send large numbers of records can exceed the 60-second timeout window. This is the most common cause of timeouts in TrackVia integrations.

How to fix it:

  1. Open the recipe step that is timing out.
  2. If the step retrieves records (for example, a Search Records action), reduce the number of records returned per request by applying more specific filters or lowering the page size limit.
  3. If the step sends a large batch of records, split the operation into smaller batches using a Repeat loop with a manageable page size (typically 100–500 records).
  4. Test the recipe after adjusting the batch size to confirm the timeout is resolved.

See Workato Recipe Design Best Practices for guidance on designing recipes that handle large data sets efficiently.

Cause 2: Complex Calculations or Table Operations

TrackVia calculated fields and large table operations can increase the time required to process a record update. If the calculation involves many dependent fields or large data sets, the API response may exceed the timeout limit.

How to fix it:

  1. Identify the record type involved in the failing step. Check whether it uses calculated fields that reference many other fields or tables.
  2. If possible, simplify the calculation logic or reduce the number of fields being updated in a single API call.
  3. Consider breaking the update into multiple smaller actions — for example, update a subset of fields in one step and the remaining fields in a subsequent step.
  4. If you cannot simplify the record structure, contact TrackVia Support to review whether the calculation can be optimized at the application level.

Cause 3: Network Latency or Instability

Intermittent timeouts — failures that occur occasionally rather than consistently — are often caused by temporary network latency between Workato's servers and the TrackVia API.

How to fix it:

  1. Check whether the timeout is recurring on every job run or only occasionally. Open the Jobs tab in Workato and review the history for the affected recipe.
  2. If failures are intermittent, configure the recipe step to use Workato's built-in retry logic: in the action step settings, enable On error handling and set a retry policy with a short delay (for example, retry 3 times with a 30-second interval).
  3. If failures are consistent, network latency is likely not the root cause — review the other causes in this article.
  4. If intermittent failures persist despite retry logic, contact TrackVia Support to determine whether there is a platform-level connectivity issue.

Cause 4: TrackVia Server Load

During periods of high server load — such as when many users are simultaneously accessing the platform or when large background processes are running — the TrackVia API may respond more slowly than usual, causing otherwise normal requests to time out.

How to fix it:

  1. Check the TrackVia status page or contact TrackVia Support to determine whether there is a known performance issue or ongoing maintenance window.
  2. If the timeout coincides with a scheduled batch operation (such as a nightly data import), consider rescheduling your recipe to run at a less busy time.
  3. Add error handling to your recipe so that timeout failures trigger an automatic retry after a delay, rather than stopping the recipe entirely.
  4. If high server load is a recurring issue during your integration's scheduled run time, work with TrackVia Support to evaluate whether the integration schedule can be optimized.
⚠ App Script logs: If your integration uses TrackVia App Scripts as part of the workflow, check the App Script logs in TrackVia for any errors or long-running operations that may be contributing to the timeout. App Script execution time counts toward the overall API response time.

Still Experiencing Timeouts?

If you have worked through all four causes above and the integration is still timing out, contact TrackVia Support with the following information:

  • Recipe name and job ID — available in the Workato Jobs tab
  • Full error message — copy the exact text from the failed job step
  • Frequency — whether the timeout is intermittent or consistent
  • Recent changes — any recent changes to the recipe, the TrackVia table, or the data volume being processed

Providing this information upfront will help the support team diagnose the issue more quickly.

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk