Hey,
All processes are getting stuck at waiting even if no processes are running and i have allocated 23maximum threads for instance on running state.
The process only runs when I click on the process and select "run next" - the process effectively was stuck for 12 hours without running - this bot is getting more unbearable by the second
Scheduled to 14:12 and now 2 AM, still not processed
Log id - 79079
Process not running for hours !
Re: Process not running for hours !
Really amazing how your paying customers are losing money with the bot having bugs at everything and you have gone days without replying. Can't believe this is happening really.
- martin@rootjazz
- Site Admin
- Posts: 34674
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Process not running for hours !
Restarting the app, does the issue persist?
Re: Process not running for hours !
martin@rootjazz wrote:Restarting the app, does the issue persist?
It doesn't but comes back sporadically.
- martin@rootjazz
- Site Admin
- Posts: 34674
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Process not running for hours !
How often?
Hourly? Daily? Every X days?
What actions are being run?
Are you auto cleaning the processes out?
Couple of possibilities. The clean out removes a process that has hold of the thread and keeps it in the background, so although the view doesn't show it, the process is running.
The process loses threads. This would be shown if you increase the threads to (i.e. 20, and 4 are actually working - then 16 are "lost")
The processor is just completely out of sync with the view
So when this occurs, had actions failed / been cancelled / deleted - manually / automatically), had you been playing with the threads numbers (increase /decreasing)
???
Hourly? Daily? Every X days?
What actions are being run?
Are you auto cleaning the processes out?
Couple of possibilities. The clean out removes a process that has hold of the thread and keeps it in the background, so although the view doesn't show it, the process is running.
The process loses threads. This would be shown if you increase the threads to (i.e. 20, and 4 are actually working - then 16 are "lost")
The processor is just completely out of sync with the view
So when this occurs, had actions failed / been cancelled / deleted - manually / automatically), had you been playing with the threads numbers (increase /decreasing)
???