Troubleshooting

This page collects common issues encountered when using QoderWake and how to troubleshoot them. If a problem still cannot be resolved, you can submit a problem report through the feedback channel.

​

Common Issues

​

Service fails to start

• Check whether the port is occupied: run qodercli status in the terminal to view the service status.
• Force stop and restart: first run qodercli stop --force, then run qodercli start --open.

​

Waker not responding

• Confirm the service is running (the browser can access the Web Console normally).
• Open “Settings” → “Network Settings” and run the connectivity test to check whether the model API is reachable.
• Confirm that the Waker’s Identity configuration is not empty.

​

WakerFlow stuck while running

• Check the status of each node in the run records Tab.
• Check whether an askUser node is waiting for user input.
• Confirm that the target Waker exists and is available.

​

MCP tool discovery fails

• Confirm that the MCP server process is running.
• Check whether the transport method and address configuration are correct.
• For servers that require authentication, confirm that OAuth authorization has been completed.

​

Network Diagnostics

In “Settings” → “Network Settings”:

• View the connection status and latency of each service endpoint.
• Click “Test Connection” to run the connectivity test.
• Check whether the proxy configuration is correct.

Common network issues and solutions:

​

Feedback & Support

When you encounter a problem you cannot resolve, open the “Settings” menu and click the “Feedback” option to submit a problem report. When you submit feedback, the system automatically attaches relevant diagnostic information to help locate the problem.