Hi
We are doing a POC to check how Tidal Scheduler can be used to schedule workflows published to Gallery.
while publishing this workflow to Gallery we have setup the workflow to run as service-alteryxABC because this workflow has few file operations and this service account has access to those file locations.
When we ran the workflow in Gallery manually it ran as the specified user service-alteryxABC and workflow ran without any errors.
However we we use Tidal Scheduler via API the workflow ran as Local User and gave errors.
Please help to get this solved.
Thx
Solved! Go to Solution.
Hi @PeterPerera ,
I would expect the same behaviour from both, but since it isn`t, there is a way of adding the credential to the job endpoint
Credentials | GET /user/v2/credentials | v2 |
Use POST /user/v2/workflows/{appId}/jobs if the workflow needs a Credential to run.
You can find both on the v2 page of Swagger. It has the same behaviour as v1, but you can add more parameters.
Best,
Fernando Vizcaino
Thanks Fernando for prompt reply. Yes your suggestion to use V2 credential worked here. Thank you very much as always.