The status of this idea has been changed to 'Inactive'. This status indicates that:
1. The idea has not had activity in the form of likes or comments in over a year.
2. The idea has not reached ten likes.
3. The idea is still in the 'New Idea' status.
However, this doesn't mean your idea won't be implemented! The Community can still like and comment on this idea. With enough renewed interest, this idea can be brought back into the 'New Idea' status.
Thank you for contributing to the Alteryx Community and the Alteryx Product Idea Boards!
I'm trying to make a version of this in a flow myself and its not possible because the Throttle tool isn't supported by e2/AMP. So, the part of a flow that may need to be timed out will come before the Timer I made and never actually start counting.
This would be very useful. For the the server we manage, some jobs need to run for an couple hours before failing. Other workflows should be killed if they take more than 5 min.
Lack of this feature makes it difficult to manage hundreds of workflows and maintain high workflow completion. We end up wasting hundreds of hours of compute cycles on jobs that should be killed in < 5 mins. Most often, errors are caused by data pulls errors due to congestion on system or maintenance windows. Resolution is often just killing job, then trying again.
As an alternative, can you add feature to Input Tool to timeout if data pull takes too long? Or retry after so many seconds?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.