Open from Server irregularities after upgrade
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Our Alteryx environment was just upgraded to Version 2023.2.1.226 Patch: 6 and while development is fine and everything runs as it should, the software is behaving erratically when trying to open a workflow from the server through the client, and also when saving to the server from the client.
Here is one way to produce the issue:
1 – Open the client new
2 – From the client, go to the file menu and click the option to open a workflow from the server
3 – Enter your email address and authenticate
4 – This lands me on the main gallery home page (My Workspace) as opposed to the dialogue gallery window that allows you to select a workflow to open. From that page, all I can do is open a workflow and download it somewhere, not open it directly into the client as intended.
If you close that window then try again to open a workflow from the server, it lands you on the dialogue window that allows you to select a workflow properly. Additionally, when saving a workflow, it will sometimes bring up the same gallery view as opposed to the Save Workflow dialogue box. Once again, if you just close the incorrect screen and try again, the proper save dialogue window opens.
Our IT group says they have spoken to Alteryx support about this and were told that is just how SAML authentication works in this version. I say that is nonsense. After authenticating you should continue through to what you originally clicked on, not an alternative window. Furthermore, why does it work properly after closing the incorrect screen?
All help appreciated. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Good Morning Michael
There is currently an open support case (00741016) regarding this matter at your company and the Alteryx engineers are attempting to gather a bit more diagnostic information in order to help. There have been a small number of similar cases and from the causes are seen to be
1) Incorrect SSO configuration
2) a Load Balancer without sticky sessions enabled
3) A Server/Designer mismatch (specifically when a Designer version older than 22.3 is used)
4) Firewall Blockage
Each environment is different so the problem could also be none of the above, but this is an ongoing investigation
Tom
