Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Associated objects of Task missing when the workflow execute by sasctl instead of UI #157

Open
staceychan opened this issue Mar 20, 2023 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@staceychan
Copy link

Describe the issue
When submit the workflow from sasctl , the associated objects of the user task would be missed.

To Reproduce

  1. Submit workflow with user task in it.(by sasctl and UI)
    r = mm.execute_model_workflow_definition(project_name="test", workflow_name="Workflow_1")

  2. Check the task tab in model manger ui.
    image

One of the tasks which miss the associated object was submitted by sasctl

Expected behavior
The task should show the associated object

Stack Trace
If you're experiencing an exception, include the full stack trace and error message.

Version
What version of sasctl are you using?
1.8.2
image

@staceychan staceychan added the bug Something isn't working label Mar 20, 2023
@jlwalke2 jlwalke2 self-assigned this Mar 20, 2023
@staceychan
Copy link
Author

Hi Expert,

Is there any progress on this bug? If you need any more information please let me know.
Many thanks!

@smlindauer
Copy link
Collaborator

smlindauer commented Apr 7, 2023

Hey @staceychan,

Is this for Viya 4 or Viya 3.5?

Edit: I am having a very difficult time determining where within the REST call that an associated object is being specified. I likely do not have enough workflow API experience to provide a direct solution, but I am assuming that there is a parameter missing from sasctl._services.workflow.run_workflow_definition(), which is causing this issue.

@staceychan
Copy link
Author

Hi @smlindauer,

Thanks for your reply and investigation.
We are using sasctl on Viya4.

Is there any possible timeline or schedule on this API issue?

@smlindauer
Copy link
Collaborator

smlindauer commented Apr 11, 2023

Hey @staceychan,

I am still digging in to the issue, but the workflow API side is not publicly documented and I think we may need to refactor some of the /workflow calls to utilize modelManagement/workflow instead.

Talking with my colleagues, it does look like the issue may not be caused by sasctl's usage of the APIs, but instead with the endpoint itself. I will see if I can get a more concrete answer on when to expect a fix.

@staceychan
Copy link
Author

Hi @smlindauer ,

Appreciate it! Wondering if this an issue related to the software or just api thing?
Cause if it's a viya bug, maybe you can give me some clues to start a tech support ticket.
Our customer is pushing us to get the answer since this function is about to go production.

Many thanks and have a great weekend! :)

@smlindauer
Copy link
Collaborator

Hey @staceychan,

This was a software issue on SAS Viya. To my knowledge, the bug has been fixed and should be shipped in 2023.04. If your customer is still seeing this issue after the release, please submit a tech support ticket. As context, the bug internally was labelled as "In Tasks category, no value in column Associated Objects" for the WORKFLOW.REST component.

Let me know if you need anymore details or help.

@smlindauer smlindauer self-assigned this Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants