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 some kind of issue related to Interactive Chart which appeared recently. What is funny it worked fine and from time to time I had that kind of error message but once I re-run workflow - it worked and I was able to see the chart. Since today - without any changes in formulas it when I wanted to test it I does not want to process further and rendering html file URL communicate appeared all the time. I didn't included any external files based on which chard was made - only input excel files. Now I'm confused, did you have opportunity to meet that kind of issue in your workflows before? Any ideas how to fix it highly appreciated.
apologize for late reply - In general I'm not able to put this workflow online becasue it contains confidential values. But in general when I put this workflow under interface and run it from Alteryx Gallery perspective - issue did not appear again.
I'm having this exact issue, but reversed.... Everything works correctly in my desktop designer, but I get the error when trying to run in the Service. I have 6 interactive chart tools, but the error is only listing 1 of them.
Can anyone please help to identify what is causing this issue? (I won't be able to share my workspace due to confidentiality)
I got the same error today while running an app ("Failed to load rendering HTML file URL"). It only happened once and it worked fine afterwards; I am assuming this may be a memory overload issue if there are other processes running simultaneously. It would be good to get a more conclusive answer from someone in Alteryx though.
I'm having this issues as well, in both desktop & Alteryx server/gallery. I used to get it from time to time, & I would just rerun & it would always work the second time. My users & I are now seeing this about 50-70% of the time the process is run, even on second attempts. This seems to have increase within last week or so. Any fix?