StackStorm / StackStorm/st2

Nested inquiries in a with-item task status change not propagating to the main workflow

Open
#4,825 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug inquiries status:to be verified
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

SUMMARY

In a workflow that has nested inquiries running at least 2 simultaneous nested workflows, if the inquiries are responded to in rapid succession the parent workflow gets stuck in a paused state.

STACKSTORM VERSION

3.1.0 python 2.7.5

OS, environment, install method

CentOS 7.6 in Docker all in one container

Steps to reproduce the problem

create a workflow with the following files
https://gist.github.com/m4dcoder/e84cf555f82f487d5bb31539d6f177fd

and respond to the inquires in rapid succession (less than a second apart). This can be done with
st2 inquiry respond <inquiry id> -r '{"approved": true}'; st2 inquiry respond <inquiry id> -r '{"approved": true}'

Expected Results

The workflow to finish with a succeeded state

Actual Results

workflow is stuck in a paused state

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Create the workflow files from the linked gist and reproduce the issue by running two rapid st2 inquiry respond commands. Trace the nested inquiry and parent workflow status handling, then verify that the workflow reaches succeeded rather than remaining paused.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.