v0.9.4: Enhanced Debug Logging for GraphQL Troubleshooting
π§ New Feature: Debug Flag for GraphQL Troubleshooting
What's New
- π Debug Flag: Added
debug=Trueparameter toMonarchMoneyconstructor 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:
- Upgrade:
pip install --upgrade monarchmoney-enhanced - Enable Debug: Use
MonarchMoney(debug=True) - 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_callmethod 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)