Scheduled Workflow Doesn't Work But Manual Run Does

[tmkwil]

I have a workflow published to Alteryx Gallery/Server that is scheduled to run every 4 hours.  The workflow executes with no errors but it doesn't do any work either.  However, when I run the workflow from within Gallery using the "Run" button it does work.  They are both executing the same published version of the workflow.

The workflow was developed using Designer version 2020.4.5.12471.

Gallery server is running the same version 2020.4.5.12471.

The workflow first has a Directory Input tool, which runs through a Count Records to count how many files there are to process.  If there is at least 1 I set a "Run" flag to 1 (bool), if there are no files I set the "Run" flag to 0 (bool).  This Run flag is then passed to a Batch Macro that enables/disables a container.  The container holds all the tools that actually process the file contents. 

When I run in Designer it works correctly. When I press the "Run" button in Gallery it runs correctly. When the workflow starts from a schedule it runs without errors but it seems like that container in the macro is never enabled even when a file is present.

Any thoughts on why the schedule would behave differently than a manual run?

Any thoughts on a different strategy to enable/disable execution based on files in a directory?

Primary workflow with the dir input, record count, set Run, pass to macro:

Control Parameter in the macro connected to container:

Update value with formula:

[TheOC]

hey @tmkwil 

That sounds a frustrating/confusing one.

It may be worth trying the conditional runner tool, instead of your method of disabling the container. Heres a similar situation:
https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Crew-Macro-Conditional-Runner/td-p/491...

I hope this helps!
Cheers,
Owen

[Felipe_Ribeir0]

Hi @tmkwil 

this is old, but i had a similar issue here (being able to run a workflow manually through gallery, but not with schedule). Our particular problem was with AD user permissions to the data connection (the error was happening with a database connection in our case).

If connection works with manual but not scheduled, it’s usually because in order for scheduling to work, you need explicitly be added to connection.  In other words:
•  Local, manual – can be in shared studio
•  Schedule – the individual scheduling the workflow would need to be explicitly added to share list on connection

So, the solution was to ask the server admin to add the necessary users to the share list