Skip to content

v0.9.4: Enhanced Debug Logging for GraphQL Troubleshooting

Choose a tag to compare

@keithah keithah released this 15 Sep 19:10
· 40 commits to main since this release

πŸ”§ New Feature: Debug Flag for GraphQL Troubleshooting

What's New

  • πŸ†• Debug Flag: Added debug=True parameter to MonarchMoney constructor for enhanced GraphQL logging
  • πŸ” Detailed Logging: Comprehensive request/response logging for troubleshooting API issues
  • 🎯 Targeted Solution: Specifically addresses "Something went wrong while processing: None" errors

Usage

import logging
from monarchmoney import MonarchMoney

# Enable detailed logging
logging.basicConfig(level=logging.DEBUG)

# Enable enhanced GraphQL debug logging  
mm = MonarchMoney(debug=True)  # πŸ†• New debug flag!
mm.load_session()

# All GraphQL operations will now log detailed debug information
result = await mm._investment_service.update_holding_quantity(holding_id, quantity)

Debug Output Includes

  • πŸš€ GraphQL request details (operation, variables)
  • βœ… Successful response data
  • ❌ Detailed error information with HTTP status codes
  • πŸ”΄ GraphQL-specific error messages and field validation failures

For Issue #27 Users

If you're experiencing "Something went wrong while processing: None" errors with update_holding_quantity:

  1. Upgrade: pip install --upgrade monarchmoney-enhanced
  2. Enable Debug: Use MonarchMoney(debug=True)
  3. Check Logs: The debug output will show exactly what's failing

This release helps identify whether the issue is:

  • Invalid holding IDs
  • Manual holding restrictions
  • Session permissions
  • Input validation problems

Technical Details

  • Enhanced gql_call method with conditional debug logging
  • Investment service debug instrumentation
  • Comprehensive class documentation with examples
  • Emoji-tagged log messages for easy filtering

Full technical discussion: #27 (comment)