This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We are always a few versions behind on our production environment, so it may be a while before we get to 2020.1 - if anyone else can confirm the issue is no longer present in 2020.1 that would be great
We are in 2020.1 but this issue persists for us as well. I have a workflow that is scheduled and runs fine until it is automatically disabled at some seemingly random time. The comment above regarding Mongo is interesting because we are having some issues with Mongo.
My private studio information has been stable, and no permissions on the workflow are being changed.
Pretty frustrating to put in so much work to build the work flows and achieve the desired result only to have it fail on the scheduling side. This obviously reduces/eliminates the value of this as we cannot rely on the schedule.
I rescheduled the workflow before taking note of the precise message, but I will do so tomorrow as this is likely to reoccur as the scheduled workflow has been disabled in the dead of night on consecutive days.
If I view the workflow history I can see many successful runs, and then I can see where it stopped. Here the 'Run Type" is manual (all others are scheduled), and the error messages say "Cannot access the folder ..." followed by the location of the permissioned network drive. This is followed by more errors that are of the same variety pertaining to additional objects located in the same network directory.
Of course I am wondering why our server seems to randomly disconnect from a permissioned network, and moreover when it does so why does Alteryx automatically decide to disable the workflow? First thing in the morning I am re-enabling the workflow and it runs fine, and seems to do so all day long until the middle of the night.