Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
SOLVED

Chained App in Gallery - 500 Server Error ServiceData stream ended

Alekh
9 - Comet

The first app is running correctly and the 2nd app displays the questions correctly. The 2nd app when running throws the following error: 500 Server Error ServiceData stream ended without being properly closed. I also do not get an entry in the job results in Gallery so even though it does do a portion of the workflow (since it does successfully create an output halfway through the workflow), this error prevents me from seeing what's happening. The 1st app does modify the XML of the 2nd workflow before running it as the chained app.

2 REPLIES 2
rose21wiley
5 - Atom

It sounds like you're encountering a 500 Server Error with your second app, which is preventing the workflow from completing and showing results in the Gallery. This error often indicates a server-side issue, which could be due to various reasons such as misconfigurations, resource limitations, or issues with the server itself.

Here are a few steps you can take to troubleshoot this issue: Official Site

  1. Check Server Logs: Review the server logs for any detailed error messages or stack traces that might give more insight into what's causing the error.

  2. Verify Configuration: Ensure that all configurations for the second app and the workflow are correct and consistent with the first app.

  3. Resource Allocation: Make sure that the server has sufficient resources (CPU, memory, etc.) to handle the workflow.

  4. Dependencies: Check if there are any dependencies or external services that the second app relies on and ensure they are functioning correctly.

  5. Re-run with Debugging: Try running the workflow with debugging enabled to capture more detailed information about where the error might be occurring.

Alekh
9 - Comet

So after a lot of trial and error, the issue was to do with the chained app having a batch script in the workflow with no records in the batch file. Fixed this by putting in an echo line.