Schedule status = queue

I have a workflow that I setup a schedule to run every 15 minutes past the hour.

It takes excel files from a sharePoint site, does what it needs to then dump to an Azure Data Lake Storage, Gen2.

Because I dump to Azure, the Azure fileout out tool requires the AMP Engine to be running.

When I look at the workflow to see if it has been executed, I do not see a status symbol (green = good; red = not good), instead, I see a gray clock, that looks like this....

When I hover over the gray clock, I see this...

What does this mean? It it run successfully? If so, how can I tell? If it did not...how can I tell?

Thanks....really confused on this one.

-Prpatel.

Schedule

Server

Scheduler

Accepted answers

All comments

KAkuffo

Hi @prpatel

Have you enabled schedules globally and on the user level?

1. Configuration page: https /help.alteryx.com/20221/server/alteryx-server-configuration

2. Users page - each user needs to have this permission enabled: https://help.alteryx.com/20221/server/user-roles-and-permissions

prpatel

Yes...I've already done that.

fmvizcaino

Hey @prpatel ,

What does this mean? This means that the workflow is stuck on the queue waiting to be executed.

It it run successfully? No

If so, how can I tell? The green status

If it did not...how can I tell? The red status

For workflows stuck in the queue, a few reasons:

You already have other workflows being executed and this one is waiting in the queue to be executed next.
Your Alteryx server doesn't have the AMP enabled in the system settings configuration, so the workflow will never run. You need to enable in two different places.
1. If workflows with AMP engine disabled are running successfully, this could be the reason.
2. https://help.alteryx.com/20221/server/controller
3. https://help.alteryx.com/20221/server/engine
If none of the above works for you, restarting the Alteryx Service could help correct it.

Best,

Fernando Vizcaino

prpatel

Hi.

Nothing works.

I'm running a test workflow whereby I take a dataset from SharePoint and place it in my ADLS. The Azure output file tool needs the AMP engine on.

Very simple workflow.

AMP Engine is checked in the server properties as well as checked in the workflow.

I'm running the workflow manually to test it out, and the status bar is showing as "queued to run". Its been like this for the past 30 minutes.

fmvizcaino

Hi @prpatel ,

Are you able to run workflows with the AMP engine disabled?

In the system settings, did you configure the controller and the engine?

prpatel

@fmvizcaino

I have other workflows that do not output datasets to my Azure DL, and they work fine. It's just the ones that output data to my Azure DL that are having problems.

Let me go back and check for the Engine "Both Engine" options.

I'll need help from my IT guys. I'll revert back soon.

Thanks.

-prpatel.

prpatel

That worked!!! When I selected both engines, I got it going, but then the workflow failed due to it not finding the azure tool, see below....

but I know its added to the designer that is on my server...any thoughts as to why I'm getting this error?

fmvizcaino

Hey @prpatel ,

The best option is to install the connector for all users in your server. Here is a link showing how to do it.

https://help.alteryx.com/20221/server/install-connectors-and-custom-tools

Best,

Fernando Vizcaino

prpatel

thank you....that helped, but now more issues....

The flow worked well in Designer, but now when validating and uploading to server, I get these errors....

...but workflow works well in designer, like I said.

Running in designer I get the same failure as above.

Any thoughts...?

fmvizcaino

This is a common error in python-based tools on the gallery.

Take a look here for a solution: https://community.alteryx.com/t5/Alteryx-Server-Discussions/Outlook-365-Tool-Runs-fine-on-server-machine-breaks-once/m-p/931099/highlight/true#M10747

Best,

Fernando Vizcaino

prpatel

I already had the registry edit done to when I had issues linking to sharepoint.

And even after configuring the server as you suggested in your post to '@theOC' I still got the same error.

still stumped.

-prpatel.

fmvizcaino

This could be related to the authentication method, I think.

https://help.alteryx.com/20221/designer/microsoft-azure-data-lake-file-output-tool

prpatel

@fmvizcaino

It was definitely the authentication. I used the basic end-user authentication, not recommended for private ADLS installs. I'm working with IT for service-to-service authentication; should have that up today. I'll let you know how that goes.

Also the toggle on setting the server to be able to use both analytical engines was a BIG key. Thanks for that.

-Pritesh.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703