Now that it's live, don't forget to accept your certification badge on Credly today! Learn more here.
We are currently experiencing an issue with Email verification at this time and working towards a solution. Should you encounter this issue, please click on the "Send Verification Button" a second time and the request should go through. If the issue still persists for you, please email support@alteryx.com for assistance.

Dev Space

Customize & extend the power of Alteryx. SDKs, APIs, custom tools, and more!
SOLVED

HTML GUI SDK Locking Up

rpaugh
11 - Bolide

I have a strange issue with the HTML GUI SDK.  When I select all my configuration options and click off the tool, the configuration saves without issue (and loads without issue when I click back into my custom tool).  However, if I add a textarea widget and populate it with a large access token, clicking off the tool results in the UI locking up permanently.  Here's the kicker...the access token field is not the problem.  When I add the access token value and do not check any fields for output, the configuration saves/loads without issue.  So somehow, the combination of populating the access token field and selecting fields for output is causing the lockup.  What would be the relationship between a field select list and a large configuration field?

2 REPLIES 2
BlytheE
Alteryx Alumni (Retired)

Hi @rpaugh! This sounds very unusual! Would it be possible for you to supply the source code for your tool (at least the htmls/js)? That makes it easier to troubleshoot issues like this. Thanks!

rpaugh
11 - Bolide

It appears to have been a series of masked errors.  I was able to fix the configuration save/load issue by checking the record limit value prior to executing engine flow and bypassing it when the workflow is not actually running.  From there I determined that there was an issue deep down in the code that seemed to be executing endlessly rather than crashing and/or showing an error, which is what was previously locking the UI during config save/load.  I'm working on that error now, but for the purposes of my initial question the issue is resolved.