nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Scheduled workflows in Gallery writes 0 records to output (used standard output tool)

NaveenaD

Hi community,

I noticed that when our org. switched from Alteryx 2023 to 2024.2, the standard output tools write 0 records to output files when the workflow runs in gallery using scheduler. The same workflow when runs with a click on 'run' button in gallery I don't see the 0 records issue. This is even happening with Tableau output, the dashboard data wipes out. This happens with or without AMP engine enablement.

Do you have any explanation and solution for this?

P.S.This weird behavior happens only for scheduled runs.

Publish

Gallery

Output

Schedule

Server

Tableau

Scheduler

Accepted answers

All comments

fmvizcaino

Hi @NaveenaD ,

Just to clarify, if you run the same workflow in the Gallery manually clicking the run button, does the same issue happen?

Best,

Fernando

NaveenaD

No, if I run the workflow manually form Gallery, I don't see the issue of 0 records. Only when it is a scheduled run it is creating issues. Not just with standard output tool (the spreadsheet data wipes out completely with 0 records) it also happens with Tableau output (dashbaord data wipes out)

fmvizcaino

Hi @NaveenaD ,

I have never seen this before. What is your current Alteryx Server architecture? Do you have a single server or more servers working as workers?

Best,

Fernando

NaveenaD

Hello @fmvizcaino, We have a total of 3 servers. One Gallery node and two workers.

I also saw a multiple posts regarding this same issue in the Alteryx community, like this one but I didn't find any solution though . Scheduled Alteryx Workflow Writes 0 Records to Out... - Alteryx Community

fmvizcaino

Hi @NaveenaD ,

My assumption is that when they upgraded the Alteryx Server, they may have forgotten to add the service account/Run As User to the worker node. That also assumes your input comes from a DB with user-level permissions. Lots of assumptions 😁, but trying to think outside the box here.

Depending on how your workers are configured, the default worker node for manual executions may differ from the one used for scheduled workflows.

https://community.alteryx.com/t5/Engine-Works/Alteryx-Architectures-Workload-Management/ba-p/900923

Best,

Fernando

NaveenaD

Hi @fmvizcaino Thank you for helping me think through this. Something changed over the weekend. So we have a daisy-chain of ETLs - completion of 1 kick starts the next as per schedule. When this is the setup- I learned from a colleague that if a control container or block until done tool is not implemented in the upstream ETLs and if it effects the records output sequence, somehow the following ETL output is giving 0 records. Having the control container in place for the upstream ETL fixed the issue. I didn't think earlier that an upstream ETL could impact the downstream one this way - because this didn't give us hard time in previous version. But yes, having control containers fixed the issue of 0 records in output.

fmvizcaino

Thanks for sharing the solution, @NaveenaD !

Quick Links

Popular Tags

This months top contributors

atcodedog05 19598

Qiu 15908

binu_acs 15783

MarqueeCrew 13710

apathetichell 13703