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.
I have been experimenting with scheduling jobs via the Gallery. Up until now, we have done it exclusively via View Schedules in Designer. The Gallery scheduling looks nice, and I see in the Gallery Admin Jobs screen, that there is a Migrate tab.
I check the box on a job I want to migrate. I select my account as the owner. (I am a Curator and have given myself permission all the Jobs permissions.) I click Migrate. I see the row go grey and see a spinner for a few seconds, then it goes back to normal with no change. The desired job does not appear in the Scheduled Workflows. I get no error, but it just doesn't work.
I have looked in the Gallery logs, and see references to migration, but no error messages.
The Migrate button will in fact transfer jobs scheduled on the controller to the Gallery. You need to make the choice of which Artisan will own the workflow and schedule. All screenshot are from 2019.3:
I did all of that, as I said in my original post: "I check the box on a job I want to migrate. I select my account as the owner. (I am a Curator and have given myself permission all the Jobs permissions.)I click Migrate." It doesn't do anything. No errors, no action.
I saw this message last night and thought about it some. I was wondering if you installed Alteryx Server to a non-standard location (not C:\Program Files). That's the case here and I was able to fix a Gallery problem by granting permissions for the Ran As account to an Alteryx directory. But I don't think that is the issue, for the workflows and schedules are stored in the MongoDB database.
I couldn't duplicate the error in 2019.3, which is the version we're on. This version does, however, have some issues. I reported a problem in which emails are not being sent by events in the workflows, even though the Email tool functions normally. Support emailed and stated it is a defect in the current version.
Contact firstname.lastname@example.org and they'll get back to you very quickly.