Welcome to the Alteryx Knowledge Base

InboundNamedPipe GetOverlappedResult: The pipe has been ended when running workflow in Designer
user

Created/Edited - 5/25/2026 by Michael Cordeiro | Alteryx

Description

A workflow fails in Alteryx Designer with the error:


image.pngimage.png

“InboundNamedPipe GetOverlappedResult: The pipe has been ended.”


This error typically occurs during workflow execution when the Engine process stops unexpectedly due to memory exhaustion or runtime configuration interactions.

Issue

When running a workflow in Alteryx Designer, the workflow fails with the error:


InboundNamedPipe GetOverlappedResult: The pipe has been ended

Environment
  • Alteryx Designer
  • All supported versions
Prerequisites
  • Alteryx Designer installed
  • Permission to modify workflow runtime configuration settings such as AMP and Sort/Join memory usage
  • Access to Windows system settings to review paging file size and available disk space
Cause

This error typically occurs when the Designer Engine process terminates unexpectedly due to memory exhaustion or resource contention during workflow execution.


It can also occur when runtime configuration settings such as AMP, Performance Profiling, or Sort/Join memory allocation interact with workflows that process large datasets or complex operations.

Resolution
This error usually indicates the Designer Engine process stopped unexpectedly due to memory or runtime configuration limits. Try the following troubleshooting steps:
 

 

1. Test with AMP enabled and disabled via:

Workflow Configuration > Runtime > Use AMP Engine

 

2. Disable Performance Profiling via:

Workflow Configuration > Runtime > Enable Performance Profiling

 

3. Confirm the machine meets Designer system requirements

https://help.alteryx.com/current/designer/system-requirements

 

4. Test the workflow with a reduced dataset

If the workflow succeeds with fewer records, the issue may be related to memory limits

 

5. Increase Sort/Join memory usage via:

Workflow Configuration > Runtime > Memory Usage

 

6. Confirm sufficient disk space is available

Low disk space may prevent paging file expansion

 

7. Review Windows paging file configuration

Increase paging file size if necessary

 

8. Validate database drivers are supported and up to date

 

9. Review Python tool usage

Python tools can consume large amounts of memory during execution

 

10. Review Engine logs and Windows Event Viewer for additional errors

Additional Information

If the workflow runs successfully with fewer records or on a machine with more RAM, the issue is likely related to resource availability rather than workflow configuration.


Consider running large workflows on machines with increased memory capacity when possible.

Was this article helpful?