Update audit-workflows: increase timeouts and always generate discussion reports #2057
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.
Changes
This PR updates the
audit-workflows.mdagentic workflow to improve reliability and ensure consistent reporting:1. Increased Tool Call Timeout (60s → 5 minutes)
The workflow audit agent often needs to process large log files and perform complex analysis operations. The previous 60-second timeout was insufficient for these operations, causing premature timeouts during tool execution.
Configuration change:
This sets
MCP_TOOL_TIMEOUT,BASH_DEFAULT_TIMEOUT_MS, andBASH_MAX_TIMEOUT_MSto 300 seconds (300,000 milliseconds), giving tools adequate time to complete their operations.2. Increased Total Workflow Timeout (20min → 30min)
Daily audit runs analyze all workflow executions from the last 24 hours, which can involve downloading and processing significant amounts of log data. The previous 20-minute limit was too restrictive for thorough analysis.
Configuration change:
3. Always Generate Discussion Reports
Previously, the workflow had three conditional paths (Options A, B, C) that allowed the agent to:
This conditional logic resulted in inconsistent reporting where successful audits produced no output, making it difficult to track audit history and confirm the workflow was running correctly.
Changes made:
This ensures every audit run produces a traceable discussion record, whether issues are found or not, improving visibility into workflow health and audit history.
Testing
timeout-minutes: 30in agent jobMCP_TOOL_TIMEOUT: "300000"(5 minutes in milliseconds)BASH_DEFAULT_TIMEOUT_MS: "300000"BASH_MAX_TIMEOUT_MS: "300000"Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.