Alteryx automation Desktop (Scheduling)

[AT_AYX]

Hey everyone,

I keep having the same error while scheduling a workflow (Remote Storage Error.)

This error only pops up when the workflow involves DBs (writing and/or reading) even though I configured the scheduler as this article showed https://knowledge.alteryx.com/index/s/article/Configure-Desktop-with-Scheduler-1583460917472 and added the run as a user.

The error exists whether I choose to run from disk or in Scheduler DB.

Could you please help me resolve this?

Thanks in advance

[MartyScherr]

So what I'm still trying to understand is why there is a timeout of 15 minutes when run the workflows from Scheduler via Desktop Automation and not when running from the command line utility?

[MartyScherr]

I saw this statement in an article that indicates Pre / Post SQL statements are not supported in Scheduled Workflows when using NetSuite.  Interesting that the Workflows will run Manually or via the Command Line Utility.

Resolution

• If using a read-only connection like NetSuite, modification statements cannot be used in the Pre/Post SQL statement configurations within the Input Data tool.
• Avoid using any Python-based tools.
• Do not set up connections using DCM.
• For In-DB ensure Connection Type is set to "System":

[drewwoodall]

Talked to support and basically DCM and scheduler won't work together, if I want to do it with Alteryx I'm going to have to hard code the keys into each tool and between the raw and prepare steps I'm looking at needing about 300 of them. So that's not really an optimal solution. 

Then I remembered what one of the AWS guys we've been talking to told me, whatever you can do in the console is basically an AWS CLI command. So it got me digging into the CP --recursive command and the Sync command. So since I've got a EC2 windows server w/ a network drive I'm going to be using to break up the workflows anyway, I'm looking into using task manager to just sync a formatted output straight up to the relevant S3 buckets & their folders. I wish Alteryx's output tool could create folders like the S3 upload tool can in buckets but apparently people have been asking for that since 2018 so looks like the mkdir will be the answer. Gotta have an individual folder for each unpartitioned avro file so that when it's crawled by glue it'll populate as a distinct table. 

[apathetichell]

@drewwoodall-> returning to 'use the run command tool - and auth via aws cli - don't use keys.'  There is no issue with using the run command tool on scheduler. and obviously there is more documentation and are more options to use the aws cli vs the alteryx connectors.