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.
09-28-2021 07:53 AM - edited 12-20-2022 10:51 PM
Access denied.
Hi - this is definitely an annoying bug since it makes a curator's job of debugging harder than it should be. Please fix this !
I don't agree with the resolution. As a curator, we need/should be able to see all users workflow results. This will allow for better streamlined debugging of issues. Is there a particular role that can see all workflow results no matter who runs it?
I also appreciate being able to at least see for manual jobs who ran a particular job and when, and if it resulted in an error or not. I agree this resolution might make sense for viewer and member roles (possibly Artisan), but not for curators.
FYI: We just upgraded to 2021.3.5 and if I'm interpreting the above scenarios correctly, it appears that by adding the workflow and schedule to a collection the user has access to, you can circumvent this error At least it resolves the schedules owned by others issues. Not sure if it would handle manual runs, but you can schedule to run once as a work-around.
Fixed on version 2021.4
https://help.alteryx.com/release-notes/server/server-20214-release-notes
We recently upgraded to 22.1 and we are still not able to view the workflow results of jobs run manually from a collection. I agree with the previous comment as a Curator we need the ability to see the results of any workflow or app that was run to better trouble shoot issues.
We have found a work around though we have added an Email Event on error that send the logs to via email. The only problem with this process is that the logs to not identify who manually submitted the job that errored. However, not all Artisans follow this practice so we do not always get notified.