What causes schedules to "Disable"?

Hi,

For the second time since implementing 2018.3, I've had workflow schedules suddenly update to a Disabled status on the Gallery, without being changed in any way. While it is pretty straightforward to re-enable these, it has caused us to miss a few scheduled runs.

Does anyone have any thoughts on what can cause a schedule to switch to a "Disabled" state?

Gallery

Schedule

Scheduler

Accepted answers

All comments

rahuls

Hey @Claje,

Any luck on this issue? I am also facing this in the gallery scheduler. Some of the workflows go 'disabled' from time to time.

MichaelF

Hi @Claje @rahuls

The causes can range a bit, but usually when you click Edit on the Schedule that's Disabled, there should be a message in red that will provide a reason for why it's disabled.

However, sometimes these may not be too useful. As an example, you may also see something in the Service Logs or Event Logs with something like this -

Corrupt: PersistenceContainer_MongoDBImpl_Get_Error: Record identifier is invalid <5bexxxxxxxxxxxxxxxxx1f9> collection <AS_Queue>

The Schedule tries to obtain/perform next runs based on the Queue (but also refers to other tables within the Mongodb). In this example, the record in the Queue that corresponded to this job was made corrupt, so the Schedule would never be able to calculate the Next Run and so the Schedule was disabled. There are similar instances to something like this, where an entry in one of the Mongo tables gets corrupt and the Schedule can't perform it's normal tasks.

These corruptions can come from a variety of things, most notably from abrupt stops or unclean shutdowns to the Alteryx Service, reasons ranging from a crash to the Service or the Server rebooting.

You should be able to see the error in the Gallery Logs (but you may also wish to check the Service Logs as well).

If this unexpected disabled issue is consistently occurring, I would advise to contact support@alteryx.com and explain the situation best you can.

Cheers,

Mike

Claje

Thanks for this information!

I did find out yesterday (by pure coincidence) that some administrative activities, such as a user moving between private studios, also seem to disable schedules, even if those schedules are not yet set to run.

I'm not sure of the exact reason for this, but wanted to include that finding.

rahuls

Thanks @MichaelF @Claje,

I could relate to moving between the private studios. Because I did just that before it was disabled. And I see that happens almost everytime I do that. I think it could be a bug in Alteryx or is it expected behavior?

Best,

Rahul

Kethan_Patel

This is a know issue and it has been fixed in Version 2019.2.7.63499.

davidhenington

This appears to be back with newest version. 2019.4.6.21113.

Scheduled workflows flipping to disabled with no rhyme or reason on multiple artisans.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15878

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703