improve logging and parsing of account delay - #560
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When account-delay is set, this adds the current account to the delay logs and logParser, allowing the API to know when an account is currently
pendingbefore it actually starts. This should be useful for Control API to recognize if an account is pending vs idle, when it will start, and to potentially prevent an account from being triggered to run while it's pending.For example,
[8/4/2026, 9:27:39 AM] [MAIN] [INFO] MAIN [ACCOUNT-DELAY] Waiting 76.5 seconds before starting the next account (account.1@outlook.com)