SmartERP Documentation An Ashewa Technology Solutions Platform

AI Workforce Troubleshooting, Architecture, and Tracing

Resolving tool calling timeouts, JSON parsing errors, rate limit handling, database trace inspection, and error recovery.

1. Overview & Business Value#

This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for AI Workforce Troubleshooting, Architecture, and Tracing within SmartERP.

Resolving tool calling timeouts, JSON parsing errors, rate limit handling, database trace inspection, and error recovery.

{screenshot:troubleshooting-and-architecture-overview-dashboard}

2. Prerequisites & Security Access Groups#

  • Required Modules: ashewa_ai_workforce, ashewa_ai_bridge, smarterp_ai_agents
  • Security Groups:
    • AI Workforce Operator (Technical ID: ashewa_ai.group_ai_operator)
    • AI Systems Administrator (Technical ID: ashewa_ai.group_ai_admin)
    • Governance Officer (Technical ID: ashewa_ai.group_ai_governance)
  • Master Data Dependencies: Autonomous AI agent profiles, n8n orchestrator webhooks, LLM model parameters, prompt governance rules, and human-in-the-loop approval queues.

3. Step-by-Step Configuration & Execution#

Step 1: Navigating to the Module Interface#

  1. Log into your SmartERP instance at https://smarterp.et/odoo.
  2. Open the main App Switcher (grid icon in the top-left corner).
  3. Select the AI Workforce app icon.
  4. From the top navigation bar, open AI Workforce → Copilots → Active Agents / Interaction History / Governance Queue.

{screenshot:troubleshooting-and-architecture-app-switcher-navigation}

Step 2: Creating and Parameterizing Records#

  1. Click the New button in the top-left control panel.
  2. Complete the mandatory fields in the record form:
    • Agent Name & Persona (Mandatory): Specialized AI role (Financial Auditor Copilot, SCM Copilot, etc.)
    • Target Operational Addon (Mandatory): Integrated SmartERP module (Accounting, HR, Inventory, Sales)
    • Autonomy Level (Mandatory): Level 1 Assistive, Level 2 Supervised, Level 3 Autonomous
    • Governance Gate (Mandatory): Action risk classification triggering mandatory human confirmation
  3. Configure optional operational parameters and localized tags as required:
    • Context Truncation Limit (Optional): Maximum LLM token window before historical pruning
    • Fallback Model Route (Optional): Secondary LLM provider if primary endpoint is unresponsive
    • Webhook Authentication Token (Optional): Secure shared secret for n8n workflow callback
  4. Click the Save icon in the control bar to commit the record.

{screenshot:troubleshooting-and-architecture-record-creation-form}

Step 3: Validating and Processing Transactions#

  • State Transitions: Execute operational state progression (Prompt Ingestion → Reasoning Chain → Action Proposal → Human Gate Approved → Executed).
  • Ledger & System Impact: Financial and inventory transactions executed by autonomous agents generate strict audit log entries tagging the AI Agent ID and human approver credentials.
  • Audit Verification: Automated recording of author ID, timestamp, and immutable revision history.

{screenshot:troubleshooting-and-architecture-transaction-processing-state}

Technical Architecture Overview#

SmartERP AI Workforce is built upon the muk_ai, muk_mcp, and ashewa_ai_bridge module ecosystem.

Issue 1: Tool Execution Times Out After 60 Seconds#

  • Cause: Complex database query or heavy report generation exceeded synchronous webhook timeout.
  • Solution: Configure the tool for asynchronous execution via n8n. The agent receives an immediate task ticket ID and polls for completion via callback.

Issue 2: LLM Outputs Malformed JSON Tool Call#

  • Cause: Non-deterministic model output produced unescaped string characters.
  • Solution: The ashewa_ai_bridge includes automated JSON repair heuristics. If parsing fails twice, the query is automatically routed to a higher-capability model with temperature set to 0.0.

Issue 3: Staged Action Fails With Security Permission Error#

  • Cause: The human manager approving the staged action lacks the necessary security group rights on the target model.
  • Solution: Ensure reviewing managers possess appropriate departmental write permissions in standard Odoo security groups.

4. Advanced Configuration Points#

  • Automated Actions & Scheduled Tasks (Crons):
    • AI Bridge: Heartbeat check for n8n orchestrator nodes (ashewa_ai.ir_cron_heartbeat): Runs every 10 minutes to verify gateway connectivity
    • AI Governance: Auto-archive cleared approval queue tickets (ashewa_ai.ir_cron_archive_audit): Runs daily at midnight to maintain governance ledger performance
  • Custom Print Templates & Reports:
    • AI Agent Operational Execution Audit Trail
    • LLM Token Consumption & Cost Allocation Schedule
    • Human-in-the-Loop Decision & Override Ledger
    • Agent Workflow Error & Latency Analysis
  • Multi-Company Rules: Record-level security isolation under Company 1 (Ashewa Technology Solutions S.C.), preventing cross-company ledger leakage across parent and subsidiary legal entities.

5. Comprehensive Troubleshooting Matrix#

Error Symptom / ExceptionProbable Root CauseCorrective Action / Resolution
Connection Refused: n8n webhook unreachableEndpoint URL invalid, orchestrator service offline, or network firewall block.Check n8n service health and update bridge URL in AI Workforce Settings.
Token Limit Exceeded: Context window exhaustedPrompt context exceeds configured model maximum token threshold.Enable automatic context pruning and reduce historical message buffer in agent settings.
Governance Block: High-risk action requires human approvalAgent attempted financial posting or document deletion above autonomy threshold.Review and approve the pending transaction in the Human-in-the-Loop Governance Queue.
Last updated: 2026-10-30