Workflow triggered by API can't access inputs
- 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
I already have a support ticket with Alteryx for this issue, but figured I'd also post here in case somebody has come across this before.
Server: V 2021.4.2.02731
Designer: V 2021.4
I have a workflow("workflow B") that uses a connection to our SQL server as an input.
This workflow runs just fine by itself for all these methods:
- Desktop
- Gallery(manually run)
- Gallery Scheduled
Issue when triggering Workflow B via API call embedded in Workflow A:
If I trigger Workflow B via API call from Workflow A I get the following error message from Workflow B:
"Error SQLDriverConnect: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'USWIN\myservername$"
This happens when running workflow A with the API call to Workflow B from Desktop, Gallery(manual run), Gallery scheduled run).
Both workflows(the 1st one that houses the api call trigger and the triggered one) are saved to the gallery with "set workflow credentials" set to my credentials. My credentials obviously work because running Workflow B by all other methods works just fine. It only fails when triggered via API.
I have tried with AMP enabled/disabled. I have tried using regular ODBC and DCM. All combinations result in the same error
I am an admin on the server.
- Labels:
- API
- Chained App
- Gallery
- Macros
- Scheduler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Can you confrim that you are using your own userid/token in your api call in Workflow A?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Yep... I've done this several times. The only thing I can think of is that calling a workflow via the API does not/is not passing the credentials I have it saved to "run as".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Have you resolved the issue? I met the exactly same error when trying to trigger my WF from API call.
'Error SQLDriverConnect: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NLSN\IP-0AEA58AA$''
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I don't think we did. We no longer had to use this workflow..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thank you for letting me know! I am going to ask Alteryx support to see if they have any solution
