Let’s talk Alteryx Copilot. Join the live AMA event to connect with the Alteryx team, ask questions, and hear how others are exploring what Copilot can do. Have Copilot questions? Ask here!
Start Free Trial

Alteryx Server Discussions

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

Scheduled Alteryx Workflow Writes 0 Records to Output File, Manual Run Works Fine

sschavan
6 - Meteoroid

Hi Alteryx Community,
I’m experiencing an issue with one of my scheduled workflows and could use some help troubleshooting. I have an Alteryx workflow that runs daily and outputs both a .hyper file and a .yxdb file, which have the same name. These files serve as the data source for a Tableau dashboard through Tableau Bridge. The scheduling of the workflow and Tableau Bridge has enough buffer time to allow the process to complete.

The issue:

  • Manual run: When I run the workflow manually from Alteryx Designer, it works perfectly, writing the expected data to both output files.
  • Scheduled run: When the workflow runs through the Alteryx Scheduler, it completes successfully, but the output files contain 0 records. As a result, when Tableau Bridge runs, it wipes the data from the dashboard since there are no records in the .hyper file.
  • The scheduled workflow runs without any errors, so the process itself seems to complete, but something is causing the output files to end up empty.
  • Permissions should not be an issue since the same workflow runs fine manually.

Has anyone else encountered this behavior, or does anyone have ideas on what might be causing the scheduled run to output 0 records? Any advice or troubleshooting tips would be greatly appreciated! Thank you!

1 REPLY 1
jrgo
14 - Magnetar

Unless the credential used when you run manually from Designer is the same that Alteryx Server uses when it executes a scheduled job is the same, then permissions could certainly be the issue. However, i would have also suspected that you'd see some error messages if this were the case.

 

As a troubleshooting suggestion, compare the message log from the scheduled job to the manual run and look specifically and the record counts it references on each tool message to see when records it inputted or outputted no longer match up.

 

You may also want to look at the file paths of your output tools and make sure that they didn't change when you published to Gallery. You'll want to make sure that you exclude them from being packaged assets (Workflow Options > Manage workflow assets). Including them may change the output path to something unexpected.

 

Hope this helps!