Incorrect Total Time on Auto Run during errors

[chr1syy]

Screenshot

Only did 1 Auto Run with ~30minutes before the error happened. Kept Re-trying until i restarted the app and got presented with another AutoRun-Badge for 1 hour (lvl 2 / 11).

Suspected Issue

AutoRun was working on Regex for different types of errors, the agent might have given back info about the changed code which got interpreted as error in Maestro itself and appeared as SSH Connection refused error. With retry multiple sessions got started over and over again and might have added time to the Auto Run progress through App.tsx:

           // Multiply by number of concurrent sessions so each active Auto Run contributes its time
            // e.g., 2 sessions running for 1 minute = 2 minutes toward cumulative achievement time
            const deltaMs = elapsedMs * activeBatchSessionIds.length;

            // Update achievement stats with the delta
            const { newBadgeLevel } = updateAutoRunProgress(deltaMs);

It appears that errors during active AutoRuns just set errorPaused: true while the AutoRun still counts for activeBatchSessionIds, so time gets counted.

[jeffscottward]

Which:

• Agent?
• Maestro version?

@chr1syy

[pedramamini]

Thanks for the detailed analysis, @chr1syy — your diagnosis was spot on!

The root cause is exactly as you suspected: when an Auto Run session enters an error-paused state (errorPaused: true), it remains in activeBatchSessionIds (since isRunning is still true), so the achievement time tracker continues accumulating time for that session.

We have a fix in #731 that filters out error-paused sessions from the time calculation in useAutoRunAchievements, while preserving their inclusion in activeBatchSessionIds for UI purposes (sidebar batch indicators, etc.).

Would you mind taking a look and letting us know if this addresses your issue?