Skip to content

Reporting bugs

How to report a Deplao bug effectively on GitHub - reproduce it, capture screenshots, grab the in-app log, note your environment, and what to avoid.

Found a bug? A detailed report helps the team pin it down and fix it faster. Reports with clear reproduction steps, screenshots and error logs are handled first.

In the app, open the bug-report guide quickly with the ⋯ button on the title bar → Report a bug (Báo lỗi).

How to report a bug: 5 steps

  1. Reproduce it: repeat what you did and write down each step (e.g. "Open CRM → Campaigns → Create new campaign → Error"). Note whether it happens every time or only occasionally. Update to the latest version and try again: when a new version is out, a "New v…" button appears next to the version number on the title bar.
  2. Take screenshots / record a short video: capture the screen when the error appears (Windows: PrtScn / Snipping Tool; macOS: Cmd+Shift+4). For errors that span several steps, record a short 10–30 second video (Windows: Win+G; macOS: Cmd+Shift+5). Circle or highlight the problem on the image.
  3. Grab the error log: right after the error happens (before closing the app): Settings → Logs (Cài đặt → Nhật ký) → choose "ERROR" (LỖI) (or "WARNING" (CẢNH BÁO)), type a keyword in the "Search log..." box if needed → click Copy to paste it into the issue, or Export file (Xuất file) to attach a .txt file.
  4. Note your environment: your Deplao version (next to the Deplao name in the top-left corner, or under Settings → Version log (Cài đặt → Log phiên bản)); operating system (Windows 10/11, macOS Intel / Apple Silicon, Linux); the channel and account type with the problem (personal / Business Zalo, Facebook, Telegram, Telegram Bot); whether you're on the Boss machine, an employee machine or working alone; and the feature involved.
  5. Open the issue on GitHub and follow up: a short title; a 1–2 sentence "Bug description"; numbered "Steps to reproduce"; "Expected result" and "Actual result"; attached screenshots / video / logs; "Environment". After submitting, watch for email notifications, reply promptly when the team asks for more, and confirm once you've updated to the fix.

About the log (Settings → Logs)

  • Records the app's activity and errors in real time (sending messages, account connections, sync, workflows…), filterable by level: All, ERROR, WARNING, INFO, LOG, DEBUG.
  • It only keeps about the last 2,000 lines from the current app session: closing / reopening the app clears it, so grab the log as soon as the error happens.
  • The app masks most passwords, tokens and cookies in the log; still, read it through and remove customer names, phone numbers or message content before sending.
  • For employee-related bugs: grab the log on both the Boss machine and the employee machine.

Example: a high-quality bug report

[bug] CRM campaign: messages aren't sent when more than 100 contacts are selected

Description: When running a messaging campaign with more than 100 recipients, clicking "Start" does nothing. The log (filtered to ERROR) shows a timeout line.

Steps to reproduce:

  1. Open CRM → Campaigns → Create new campaign
  2. Add contacts: every contact with the "Customer" label (about 150 people)
  3. Enter the message content → Create campaign → click "Start"
  4. → The status doesn't change and no messages are sent

Environment: Deplao v26.10.3, Windows 11, personal Zalo, working alone (no employees). Tried with 50 people (fine), 100 people (fine), 150 people (error). Attached: screenshot + log file.

Tip

This report has everything needed to track down the bug: exact reproduction steps, a comparison of results, the error log and environment details.

Common types of bugs

Bug type What to note
Crash / app freeze The last action before the error, plus a screenshot. If the app still opens: Settings → Logs → Export file.
Interface / display issue Screenshots of what you see and what you expected. Note light / dark theme, operating system, screen resolution and font size (⋯ button → Font size (Cỡ chữ)).
Account connection / sync issue The channel (Zalo, Facebook, Telegram) and the affected account, the time, and its status on the Dashboard. Try reconnecting / signing in again, and check the proxy if one is assigned.
Employee connection issue LAN or Internet, the address type (temporary / fixed), the status on the employee's title bar and on the Boss machine's Settings → Employees → Connection (Cài đặt → Nhân viên → Kết nối) tab.
Third-party integration issue Which integration (POS, shipping, payment…), what you did, the expected and actual result. Don't paste API keys into the issue.
Workflow not running A screenshot of the workflow diagram, the trigger + actions; open "Run history" in the workflow editor to see which step failed.
Slowness / lag The size of your data (number of accounts, conversations, groups), which action is slow, and a comparison with the previous version.

What NOT to do

  • Submit an issue that only says "the app is broken" with no details.
  • Submit duplicate issues: search the existing Issues first.
  • Attach sensitive information: OTP codes, passwords, API keys / tokens, cookies, customers' phone numbers or messages.
  • Use issues for how-to questions: read these docs first (in the app: Settings → About (Cài đặt → Giới thiệu)), or ask through the ⋯ → Support (Hỗ trợ) button on the title bar. See also the FAQ.
  • Combine several different bugs in one issue: one bug per issue makes it easier to track and confirm the fix.
  • Mix feature requests into bug reports: open a separate issue for suggestions.
PreviousFrequently asked questions

Didn't find your answer?

Message us on Telegram