Known Errors and Solutions

This guide is designed to help you quickly identify and resolve common issues when running workflows in Ecoscope. Whether you're working with Subject Tracking, Events, or Patrols, each entry in this guide includes:

Error ID – The message or code displayed after a failed run

Suggestion – Recommended actions to help resolve the issue

How to Find the Error ID

When a workflow fails, the error message can be found in the Metadata panel of the workflow. Click on the failed workflow to open its metadata and look for the red-highlighted error block near the top.

Example: 

Use this guide to troubleshoot failed workflows, unexpected behavior, or confusing messages. If you are unable to resolve the issue after troubleshooting with this guide please make sure to contact the Support team with the metadata information. 

Troubleshooting Guide

Any

Error ID Suggestion
ERClientPermissionDenied('Forbidden.') Check whether the EarthRanger user associated with this data source has permission to access the specific data being queried.
For example, if the workflow references a subject group, make sure the user has access to all subjects in that group.
InvocationTimeoutError: The workflow timed out. Consider reducing the amount of data being processed.

The workflow took too long to complete. Try the following to reduce processing time:

  • Shorten the time range selected in the configuration
  • Limit the number of groupers or categories used
  • Reduce the volume of input data (e.g., fewer subjects or events)

If you're working with large or high-resolution datasets and the above steps don’t help, try running the workflow using Advanced Run > Heavy Duty Workflow Run.
ValueError('cannot insert TemporalGrouper_%Y, already exists') You’ve added the same grouper more than once.
Go to the configuration form and remove the duplicate grouper entry before running the workflow again.
The maximum number of workflows are already running (X total and up to Y heavy duty). Please wait for one of them to finish, then try again. Ecoscope workflows run on secure cloud servers, and each account has a set number of concurrent workflows it can run at once to ensure resources are shared fairly among users. If you see this error, it means you’ve reached that limit. Once one of your current runs completes, you’ll be able to start another. At times of high traffic, or if your account has been especially active in the prior 24 hours, you may also experience reduced limits. Heavy duty workflows use more resources and can lower the number of additional workflows available until they finish.
Workflow https://<WORKFLOW_NAME>.ecoscope.io/ is temporarily unavailable. Please try again in a few minutes. If the problem persists, please contact support. Details: ReadTimeout During traffic spikes, the cloud servers that run workflows may be temporarily saturated and unable to keep up with demand, which can trigger this error. In most cases, it resolves quickly — wait a minute or two and then click Run Again from the workflow’s kebab menu (⋮). If the error continues after several attempts, spaced a minute or more apart, contact support as it may indicate a broader outage. Note that <WORKFLOW_NAME> will be replaced with the name of the workflow you were trying to run (e.g., patrols, events), and while ReadTimeout is the most common detail shown, the same guidance applies regardless of what appears.

 

 
 

Events

Error ID Suggestion
v14.1.0 - grouped_fd_colormap - ValueError('could not broadcast input array from shape (2,) into shape (0,)') Check the input data for the workflow. This error may occur when the workflow attempts to process incompatible or empty data structures.
v14.1.0 - get_events_data - ERClientException('Failed to call ER web service at https://......414 This is a known bug. Try selecting a subset of the available event types and re-running the workflow.

 

 
 

Patrols

Error ID Suggestion
v20.0.0 - patrol_obs - ERClientException('Failed to call ER web service at https://.... 504 upstream request timeout') This error can occur when the workflow times out while trying to fetch patrol data.
Try reducing the time range or number of patrol types selected in the workflow configuration. This is a known issue and narrowing the query can help avoid the timeout.

 

 
 

Subject Tracking

Error ID Suggestion
v14.0.0 - subject_traj - Trajectory data left after applying segment filter').  This error means the segment filter settings are too strict, and no trajectory data remains after filtering.
Try relaxing the values for minimum segment length, duration, or speed in the advanced configuration to ensure some movement data is retained.