Running SyncApp in Debug Mode

Lesson 4.7 ⏱ ~12 min

💡 Why This Matters

Bugs in SyncApp integration code can be subtle — wrong field mapping, incorrect data transformation, missing records. Debug mode with GoLand or VS Code lets you set breakpoints and inspect the exact data being transformed.

🎯 What You'll Learn

How to run SyncApp in debug mode using GoLand's debugger
How to set breakpoints in entity sync functions (e.g., patient sync)
How to verify data verification status in WAM before your synced data becomes visible
Reading SyncApp console logs to confirm sync cycles are running
How the '76 invalid records' status in WAM is expected and what it means

▶ Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

Debug mode runs SyncApp with an attached debugger (GoLand or VS Code). Set breakpoints in the patient sync function, then run in debug mode. The debugger pauses execution at breakpoints, allowing inspection of the data being transformed. After completing a cycle, WAM shows your machine's hostname as the active SyncApp host. The location must be verified in WAM before patient data becomes visible in the Weave portal. SyncApp runs every 15 minutes — if you leave debug points active, the next cycle will also pause at them. VS Code and GoLand debug configurations are documented in the onboarding ticket.

🏷 Key Concepts

Debug Mode GoLand Debugger VS Code Debugger Breakpoints Entity Sync Functions Invalid Records Verification Requirement Console Logs

⭐ Key Takeaways

01Debug mode is your primary tool for investigating data transformation bugs

02After running in debug mode, always verify the location in WAM to make patient data visible

03SyncApp cycles every 15 minutes — active breakpoints will pause every cycle, not just the first

04Invalid record counts in WAM are common and expected — you'll learn their significance as you work

05Both GoLand and VS Code are supported — use whichever you're more comfortable with

Your Progress