Skip to main content
Support

Troubleshooting

Diagnose common service, task, connector, knowledge-base, and @Waker issues.

Find the section that matches the symptom, or search for Console, Login, Autonomous Work, WakerFlow, Knowledge Base, Connector, Update, or @Waker. Troubleshoot in this order: Local Service → Login and Network → Device and Waker → Task Configuration → External Capabilities. Change one item at a time and retest immediately. If the issue remains, record the timestamp and time zone, error text, relevant IDs, and logs.

The console cannot be opened

qoderwake status
qoderwake start --open
qoderwake portal --no-open
qoderwake restart
Check the service status, start the service, and obtain the actual access address in sequence; restart if it still cannot be opened. Don't just use fixed ports from bookmarks. Completion criteria: QoderWake status shows that the service is running, the address output by QoderWake portal --no-open can be opened, and the Web Console page has completed loading. If restart refuses execution due to an invalid login, and you confirm that you only want local mode: 
qoderwake restart --force
This parameter will start in local mode; you should log in again when remote capabilities are required.

Login or remote capabilities not available

  1. Execute QoderWake whoami to check the account; execute QoderWake login if you are not logged in or the account is incorrect.
  2. After logging in, check your account again and run network diagnostics.
  3. When the remote device is still invisible, confirm that the device uses the same account and refresh the device page.
Completion criteria: QoderWake whoami can display the expected account number, the Gateway authentication in network diagnosis has passed, and the target remote page can be loaded normally.

Waker does not respond or the task does not end for a long time

  1. Confirm the status on the task dashboard; when "operation required", go to the original task for processing.
  2. When queuing or executing for a long time, check that the device is online, the service is running and not sleeping.
  3. Open the original task to check for errors and send a minimal test message; if it still fails, check the directory, model, connector and permissions.
Completion criteria: After creating a minimum test message, the task can enter the execution from the queue, and finally return a reply or clarify the error.

Autonomous Work is not running

  1. Confirm that the task is enabled and check the time, time zone, event/API request, validity period, and number of runs.
  2. When using the local directory, confirm that the device is powered on, the service is running, and it is not sleeping when triggered.
  3. Check run history and distinguish Not Triggered from Triggered but Failed. After fixing the issue, run the task manually before waiting for the next real trigger.
Completion criteria: A new run-history record appears with the expected start time and trigger method, and its complete result can be opened.

WakerFlow gets stuck, fails or has incomplete results

  1. Open Run History and identify the current phase, Waker node, and whether the flow is waiting for user input.
  2. When input is required, respond in the run detail. When a Waker node fails, inspect its error, node result, and raw event.
  3. Verify run parameters, Wakers, knowledge bases, connectors, and permissions. Use business logs to locate the phase, but use the Waker-node result and final return value to judge the outcome.
  4. After repairing, re-execute from "Run" in the upper right corner.
Completion criteria: All required Waker nodes in the new run succeed, the run record shows completion, and the final return contains every field required by the flow contract.

The task board has no tasks or the status is not updated

  1. Clear the Type, Group, Waker, and Status filters and toggle between list/swim lane views.
  2. Expand the parent task of the group task and return to the original task to confirm that the task has indeed been created.
  3. Re-enter the dashboard; run network diagnostics and check permissions if the source read fails.
Completion criteria: After clearing the filter, you can find the target task, the status is consistent with the original task details, and you can jump to the source page normally.

Knowledge base information cannot be used

  1. Open the knowledge base and confirm that the source exists, processing completed, and the extracted content is readable.
  2. Open Cards and confirm that the source was compiled; run a manual compilation if necessary.
  3. Check the binding on both the knowledge-base list and the Waker detail page.
  4. Start a new chat and ask a question with a clear answer in the source.
  5. If the answer remains inaccurate, remove obsolete or conflicting material, recompile, and retest.
Completion criteria: Waker can accurately answer known facts in the information, and the answers are consistent with the current version of the information. If a shared knowledge base cannot be edited, check the member identity and view, edit, or management permission.

Connector not available

  1. Enter Waker details → "Connectors" to check the configuration, authorization, connection status and tool list.
  2. Go to Waker's "Permissions" to confirm that the relevant tools are allowed to be used.
  3. Create a new minimal test task that only calls the connector.
Completion criteria: The connector is available, its tools can be discovered, and a minimal test task calls it successfully and returns a result. Connectors are managed in the "Connectors" of Waker details. Don't paste tokens or keys into chats, knowledge bases, or logs.

Network diagnosis failed

Enter "Settings" → "Network Diagnosis", run the complete diagnosis and deal with the failed items:
Failed ItemsPriority Check
Gateway authenticationWhether the login is valid, the account is correct, and the system time is accurate
Machine registrationWhether the local service is running, whether the current device has been registered, and whether the accounts are consistent
Work backhaulWhether the device is online, whether the corporate network or firewall blocks long connections or return requests
At the same time, check the system time, DNS, corporate network, firewall and security software; switch the network to retest if necessary, and record the failure summary. Completion criteria: After re-diagnosis after repair, Gateway authentication, machine registration and Work callback are all shown to be passed; then the original remote operation can also be successful.

update has been downloaded but the version has not changed

  1. Go to "Settings" → "Update Apps" and confirm that the update has been installed.
  2. Restart the service:
qoderwake restart
  1. Execute QoderWake status, then go to "Update Application" to check the version.
Completion criteria: After restarting, the running version is consistent with the installed version, and the page no longer displays "restart required". When just running QoderWake update without restarting, the current service may still be using the old version.

View the log and submit feedback

1. Positioning log Default main log location: 
${QODERWAKE_HOME:-$HOME/.qoderwake}/logs/qoderwake.log
First choose a search method based on the question: 
# Last 200 log entries at warn level or above
qoderwake log --level warn --limit 200

# Search by keyword
qoderwake log --keyword "keyword" --limit 200

# Search by traceId or sessionId
qoderwake log <traceId>
To keep checking for new posts use QoderWake log -f. Only one position parameter traceId, --trace-id and --keyword can be selected at a time; --clean can be added to simplify the display. 2. Collect problem evidence Record the time of occurrence and time zone, version and operating system, task name or ID, steps to reproduce, error text and traceId/sessionId; do not submit credentials. 3. Submit feedback 
qoderwake feedback --email "your-email@example.com" --message "Problem description"
Increase --waker-id <wakerId> when associated with a Waker. Completion criteria: The command returns feedback id. Save this ID and use it to locate the feedback record in subsequent communications. Submitting feedback requires a valid login; the problem description parameter is --message.

@Waker issues

The bot is in the group, but no pending request appears

  1. Open @Waker → IM Connection Management and confirm that the bot connection is available.
  2. Confirm that the bot is in the group, then mention it in a new ordinary message.
  3. Open @Waker → Pending Requests and verify the chat, requester, and connection identity.
  4. If no request appears, review the connection scope. When a pairing code is available, generate a one-time code and complete pairing in the target group.
  5. After approval, mention the bot again and run a read-only task.
Completion criteria: The group appears in the enabled-session list, the message creates a task, and the response returns to the group.

The session is enabled, but the bot does not reply

  1. Confirm that the session is active and @Waker is enabled.
  2. Check that the IM connection is online, the bot remains in the group, and it can receive and send messages.
  3. Confirm that at least one Waker is enabled and a default Waker is selected.
  4. Check the Waker's device, project, model, connectors, and permissions.
  5. Send a minimal task that does not require external tools and inspect its state on the Task Board.
Completion criteria: The message appears on the Task Board, the corresponding Waker executes it, and the result returns to IM.

The request routes to the wrong Waker

  1. Give every Waker a distinct name and responsibility.
  2. Use the default Waker only for requests whose responsibility is unclear.
  3. Rewrite overlapping roles with explicit inputs, outputs, and boundaries.
  4. In the same test chat, send two tasks with clearly different responsibilities and inspect the actual executor.
After changing routing configuration, rerun the same fixed test set so the results can be compared.

A file or final result is missing from IM

  1. Open task details and confirm completion and the artifact's actual location.
  2. Check whether the IM channel supports native attachments or clickable links.
  3. If it does not, retrieve the file from the QoderWake task artifact or team project and return an accessible location.
  4. Never send passwords, tokens, or customer-private data as attachments.
Completion criteria: A group member can reach the final artifact from the original chat or an explicit link, with the expected access permission. Other common symptoms:
SymptomActionCompletion criteria
Image question is misunderstoodAdd a text question and context, point to the relevant area, and provide raw data for complex chartsThe answer addresses the specified area
A restricted page imports as empty content or 404With authorized access, export it to a supported file, upload, compile, and retestProcessing and compilation finish, and the Waker can use the content
Get Started
Work Management
Employee Resources
Best Practices
Configuration
Support