fix: reduce aggressive orphaned position monitoring frequency

- Changed position monitor interval from 30 seconds to 5 minutes (300s)
- Reduced verbose logging in position monitor API
- Only log orphaned order checks when orders are actually found
- Prevents log flooding while maintaining functionality

- 90% reduction in monitoring frequency (30s → 300s)
- Cleaner logs with less noise
- Still catches orphaned orders effectively
- Better system performance with reduced API calls

 Verified:
- Automation page now runs monitor every 5 minutes
- Position monitor API only logs when orphaned orders exist
- System still functions correctly for cleanup
This commit is contained in:
mindesbunister
2025-07-26 20:26:45 +02:00
parent 60df2b4667
commit e0d1344421
2 changed files with 3 additions and 4 deletions

View File

@@ -81,7 +81,6 @@ export async function GET() {
}
} else {
// NO POSITION DETECTED - Check for orphaned orders and cleanup
console.log('📋 No active positions detected - checking for orphaned orders...');
try {
// Check for any remaining orders when we have no positions
@@ -97,6 +96,7 @@ export async function GET() {
const activeOrders = ordersData.orders || [];
if (activeOrders.length > 0) {
console.log('📋 No active positions detected - checking for orphaned orders...');
console.log(`🎯 Found ${activeOrders.length} orphaned orders - triggering cleanup...`);
// Trigger automated cleanup of orphaned orders
@@ -140,7 +140,7 @@ export async function GET() {
};
}
} else {
console.log('✅ No orphaned orders found');
// Only log occasionally when no orders found (not every check)
result.orphanedOrderCleanup = {
triggered: false,
success: true,

View File

@@ -40,8 +40,7 @@ export default function AutomationPageV2() {
fetchBalance()
fetchPositions()
fetchMonitorData()
fetchMonitorData()
}, 30000)
}, 300000) // 5 minutes instead of 30 seconds
return () => clearInterval(interval)
}, [])