Intermittent Issue: Single Action Triggered Twice in an Action Chain
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
We have few incidents of actions inside the chain triggered/executed twice within a chain which causing issue to the customer. We are unable to track down the root cause. The action chain is being triggered via webhook.
STACKSTORM VERSION
Paste the output of st2 --version: st2 3.7.0, on Python 3.8.10
OS, environment, install method
Post what OS you are running this on, along with any other relevant information/
- e.g. Docker, Vagrant, Kubernetes, etc. Describe how you installed ST2: Docker in our CaaS Container.
- e.g. one-line install, custom install, etc --> Kubernetes HA. System Requirement is aligned with St2 doc
Steps to reproduce the problem
Unable to reproduce the problem. Is there any way that I can identify the root cause?
Attempted to replicate the issue via StackStorm UI to execute the chain. No duplicate action is triggered.
Expected Results
It should only trigger each action once within the chain.
Actual Results
This is an intermittent issue. We are hoping to see whether they is any recommended way to reproduce the problem.
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing webhook-triggered action-chain execution in the StackStorm deployment and investigate the intermittent duplicate execution; done means identifying the cause and confirming that each action runs only once.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, python
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100