advpl-debugging

Diagnose ADVPL and TLPP errors using Conout and FWLogMsg logging.

176|37|Updated Mar 4, 2026

Search Tags:#performance #debugging #error handling #logging #advpl #tlpp #protheus

Ready to run

npx skills add https://github.com/thalysjuvenal/advpl-specialist --skill advpl-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: advpl-debugging
Source: https://github.com/thalysjuvenal/advpl-specialist/tree/main/skills/advpl-debugging
Command: npx skills add https://github.com/thalysjuvenal/advpl-specialist --skill advpl-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides a systematic methodology and practical tools to diagnose and resolve complex errors in ADVPL/TLPP code, ensuring smoother Protheus application development and maintenance.

Core Features & Use Cases

Error Diagnosis: Pinpoint the root cause of compilation, runtime, performance, and database lock issues.
Logging & Tracing: Utilize Conout and FWLogMsg for detailed error tracking.
Use Case: When a critical Protheus function fails intermittently with a cryptic error, use this Skill to analyze logs, add targeted debugging statements, and identify the exact line of code causing the problem.

Quick Start

Use the advpl-debugging skill to help diagnose a 'Variable does not exist' error in your ADVPL code.

Frequently Asked Questions about advpl-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug a 'Variable does not exist' error in ADVPL?▼

To debug a 'Variable does not exist' error in ADVPL, you analyze compilation logs and add targeted debugging statements to pinpoint the exact code line. This Skill provides systematic methodologies for tracing variable scope and resolving such compilation failures.

What is the best way to log and trace runtime failures in TOTVS Protheus?▼

The best way to log and trace Protheus runtime failures is using Conout and FWLogMsg. These tools provide detailed error tracking capabilities to help identify the root cause of intermittent runtime issues within the TOTVS ecosystem.

How do I resolve database deadlocks and performance bottlenecks in TLPP code?▼

To resolve database deadlocks and performance bottlenecks in TLPP code, you diagnose transaction conflicts and query inefficiencies. This Skill provides systematic methodologies to identify database lock issues and optimize ADVPL performance bottlenecks.

Why does my Protheus function fail intermittently with a cryptic error?▼

Intermittent Protheus function failures with cryptic errors stem from unhandled runtime exceptions or AppServer issues. You resolve this by utilizing error block usage and analyzing logs to add targeted debugging statements for root cause identification.

What are common debugging pitfalls when working with ADVPL and AppServer?▼

Common ADVPL and AppServer debugging pitfalls involve misinterpreting error blocks and overlooking AppServer configuration issues. This Skill details these limitations and provides precautions to avoid common traps during error diagnosis and log analysis.