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.
Hi all, first time posting to the Alteryx community here.
My issue has to do with the Salesforce Input tool. After some heavy googling and roaming around the community I did not find a case handling my error.
I have created an Alteryx workflow through Alteryx Designer where I fetch data using the Salesforce Input tool. I'm loading quite large amounts of data (1-2 million rows), so I have split up the Salesforce inputs so that each call won't be too big.
It works just fine when I run it locally through Designer, and manually on the Server (runtime ~25-30 minutes). However once I put the workflow on a nightly schedule I notice the workflow failing.
There is a setting inside of the server that you can change to increase the time for workflows running longer than X seconds.
From Alteryx Designer on the Server, go to Options --> Advanced Options --> System Settings. (Note: if you are running Alteryx Server and don't see the System Settings, you will need to contact your server administrator and have them help you make changes to the System Settings). Click 'Next' until you get to the Worker Configuration. If the 'Cancel jobs running longer than (seconds)' option is checked, the seconds can be increased here.
This message will be generated for scheduled workflows and workflows being run from a gallery if the option has been checked and the workflow runs longer than the setting allows.
I've done some experimenting and I noticed that my issue is solved when I execute the same workflow using the Salesforce input a second time 15 minutes after the first attempt. The first attempt will always fail but the second one seems to work all the time (at least for all daily schedules since this case was created).
I'm not sure if this should be accepted as a solution since it does not make sense to have two identical consecutive workflows.
I think it has to do with what @VianneyM suggests. It takes too long time to fetch all data via the API since there are other workflows running in parallel, occupying necessary resources to finish the API call, hence the API call will be open longer than the threshold allows.
I'm looking into another solution in the future, where I will only fetch the change of data for every API call hence making each API call smaller. I guess I will need some kind of middle/temp storage for this that works on scheduled basis on the Server to make this work.