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

Workflows stuck on "EXECUTING" status and not able to execute API individually #1378

Open
OneG14 opened this issue Apr 30, 2024 · 1 comment

Comments

@OneG14
Copy link

OneG14 commented Apr 30, 2024

Describe the bug
The webhook I am using in my workflows is just getting stuck on "Executing" stage

Version
Shuffle Version : 1.1.0
My Instance details : 8 cores, 16gb
docker version:
Client: Docker Engine - Community
Version: 24.0.4
API version: 1.43
Go version: go1.20.5
Git commit: 3713ee1
Built: Fri Jul 7 14:52:35 2023
OS/Arch: linux/amd64
Context: default

Server: Docker Engine - Community
Engine:
Version: 24.0.4
API version: 1.43 (minimum version 1.12)
Go version: go1.20.5
Git commit: 4ffc614
Built: Fri Jul 7 14:50:59 2023
OS/Arch: linux/amd64
Experimental: false

** Debugging**
I tried to stop and start the docker compose many times but still the same issue...
Initially my instance was 4cpu, 8gb system I have upgraded the instance to 8cpu, 16gb thinking that might be the issue..
I have downgraded orborus and checked with different versions but that didn't do anything either...

Screenshots
image
image

@frikky
Copy link
Member

frikky commented May 5, 2024

Describe the bug The webhook I am using in my workflows is just getting stuck on "Executing" stage

Version Shuffle Version : 1.1.0 My Instance details : 8 cores, 16gb docker version: Client: Docker Engine - Community Version: 24.0.4 API version: 1.43 Go version: go1.20.5 Git commit: 3713ee1 Built: Fri Jul 7 14:52:35 2023 OS/Arch: linux/amd64 Context: default

Server: Docker Engine - Community Engine: Version: 24.0.4 API version: 1.43 (minimum version 1.12) Go version: go1.20.5 Git commit: 4ffc614 Built: Fri Jul 7 14:50:59 2023 OS/Arch: linux/amd64 Experimental: false

** Debugging** I tried to stop and start the docker compose many times but still the same issue... Initially my instance was 4cpu, 8gb system I have upgraded the instance to 8cpu, 16gb thinking that might be the issue.. I have downgraded orborus and checked with different versions but that didn't do anything either...

Screenshots image image

Hey! Please send me an email so we can set up a call and fix this. frikky at shuffler dot io

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants