In ABP Studio 3.1.1, task execution takes an extremely long time with no way to verify whether the task is still running. The status only stays as Running without any numeric progress updates. I once waited for an hour yet there was no visible change.
When clicking Stop Task, the stopping process itself hung for another 20 minutes while remaining in the stopping state. After closing ABP Studio and restarting it, the application crashed several times on launch. Once it finally opened, the previous working session was lost and could not be recovered.
I re‑initiated the task with the execution speed set to xhigh, but the same issue persisted — the task got stuck at the Running status again with no activity indicator. It becomes impossible to judge whether I should keep waiting for completion.
The core pain point is the lack of real‑time, fine‑grained progress feedback. Suggestion: Add more granular, real‑time progress tracking on the ABP Studio client to show ongoing work for long‑running background tasks.
Key terminology kept consistent with ABP Studio UI
- ABP Studio 3.1.1
- Running (status label)
- Stop Task
- Session
- xhigh (speed option)
- long‑running background tasks
- fine‑grained real‑time progress feedback
3 Answer(s)
-
0
Hi,
The description alone isn't enough to tell which step got stuck. Every step of an agent run (model response, shell commands, starting applications, the package analysis on the first message) has its own timeout, and a timeout shows up as an error instead of staying at Running, so we need the log to see what happened.
Could you send this file to liming.ma@volosoft.com:
- Windows:
%USERPROFILE%\.abp\studio\ui\logs\abp-studio-ui-logs.txt - macOS / Linux:
~/.abp/studio/ui/logs/abp-studio-ui-logs.txt
And a few details:
- Operating system and version.
- The provider and model selected under Settings > Models (OpenRouter / OpenAI / Anthropic / custom).
- What the task asked the agent to do, and the status text shown above the chat input while it was stuck (Thinking... / Running: xxx / Updating analysis...).
- Whether this was the first message of a new session, and roughly how many packages the solution has.
About the lost session: a new session is only written to
.abpstudio/agents.dbunder the solution folder after its first turn completes. If the turn is stopped or Studio is closed before that, nothing is saved and the session won't show up in Archive either. We'll change this.Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) - Windows:
-
0
After checking the logs, the issue is likely caused by a network problem.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
