Skip to content

Common Issues

The check command couldn’t locate the source .md file referenced in the compiled pipeline’s @ado-aw header.

Solution: Ensure the markdown source file hasn’t been moved or renamed since compilation. Recompile with ado-aw compile.

YAML front matter must be valid YAML between --- delimiters.

Common causes:

  • Unquoted strings containing special YAML characters (:, #, {, })
  • Incorrect indentation (YAML uses spaces, not tabs)
  • Missing required fields (name, description)
---
# ✗ Bad -- colon in unquoted string
description: Agent: does things
# ✓ Good -- quoted string
description: "Agent: does things"
---

The agent can only access explicitly allowed domains. If your agent needs to reach an external service:

  1. Check if a runtime enables the domain (e.g., runtimes: [python] enables pypi.org)
  2. Add custom domains via allowed-hosts: in front matter
  3. For broader access, use ADO permissions: with a service connection

Stage 2 (Detection) may reject safe outputs that appear to contain:

  • Prompt injection patterns
  • Embedded secrets or tokens
  • Malformed parameters

Solution: Review the agent’s output proposals. Ensure generated content doesn’t accidentally include patterns that resemble secrets (long base64 strings, key-value patterns matching password=...).

cargo build fails with missing dependencies

Section titled “cargo build fails with missing dependencies”

Ensure you’re using the Rust 2024 edition toolchain:

Terminal window
rustup update
rustup default stable

Some tests require shellcheck to be installed. If missing, tests are skipped (unless ENFORCE_BASH_LINT=1 is set).

Terminal window
# macOS
brew install shellcheck
# Ubuntu/Debian
sudo apt-get install -y shellcheck

If your issue isn’t covered here:

  1. Check the GitHub Issues
  2. Review the Reference documentation for field specifications
  3. Run with --debug for verbose logging: ado-aw --debug compile ./agent.md