Scheduled workflows not running /running arbitarilly

Question

Hi All,

We are facing issues with sheduled worklfows not running/running arbitairlly on the server...This was never a case before and we are finding to trace back where the issue is and how we can fix the same. All our alteryx workflows populate our datawarehouse and this is rather a high impact for us...

Few issues we encountered (not sure if they are related)

1: We have configured a new alteryx server to act as a worker node to help with the worklflow processing.

2: We had an alteryx server failure where the schedules were all empty and apprently there was a lock on the Mongo DB. We had to restart the alteryx service and it all strted working...

Since the server failure we feel that the schduels are not working/working how it was previously...

Can anyone help on how we can identify the issue and recitify these as we are having a big impact?

Thanks

Newstart2020 · Answer

joshuaburkhow

Yes , i raised this as a support query. I have provided them with the logs but havent heard back after that...Most of our key workflow schedules are run on disc on the server . we do not have much schedules on the gallery. I initialized last night one schedule to run once at a specific time and it got triggred...

Is there a way to check if the scheduler is corrupted??

regthe fix the temp table in Mongo, did u recreate schedules one by one??

joshuaburkhow · Answer

Hey @Newstart2020

A couple things for you. Since this is a high priority issue for you I would hope you've reached out to support@alteryx.com so they can have a look.

Schedules can be affected in many different ways:

* If your users don't sync up to a studio - so say you deleted a studio for some reason but the user is still pointing to that studio. That has caused Schedules to be disabled
* If you switch studios - if a user schedules a workflow in studio A and then switches to Studio B and is associated to Studio B when that Scheduled job in Studio A runs it will get disabled

As far as your new worker. I'd recommend assigning a tag and running jobs through that worker to ensure it's setup right. You also need to ensure that every worker you setup has all the drivers that are needed.

In the past I had a schedules table get corrupted. The way I fixed it was to built a temp document (table) in mongo and move all of the schedules to it. Then 1 by 1 bring them back and ensure they are working. You'll find any issues to address that way.

Hope this helps!