Support
Before you ask
Section titled “Before you ask”Most problems have a known cause and a known fix. Check Troubleshooting first — it covers failed runs, blocked merges, stuck workflows and held credits.
What to include
Section titled “What to include”The more specific your report, the faster it can be resolved. Include:
- The change-set ID — shown in the State tab
- The service name — if the problem is scoped to one service
- The status reason — the text shown in the change set panel
- When it happened — roughly, with your timezone
- What you expected — one sentence
Where to reach us
Section titled “Where to reach us”- Discord — discord.gg/AUUWcMca6H for questions and discussion
- GitHub — github.com/delta-ai-dev for issues with the published output
Reporting a bug in generated code
Section titled “Reporting a bug in generated code”If the generated code is wrong — a test that does not test what it claims, a specification that contradicts itself, an implementation that does not match its spec — that is worth reporting. Include the repository and the file.
Generated code is meant to be reviewed. A defect that survives review is a defect in the product.
Feature requests
Section titled “Feature requests”Tell us what you were trying to do and what stopped you. The specific workflow matters more than the proposed feature.
Security issues
Section titled “Security issues”Do not report security issues publicly. Contact us directly through Discord and we will respond privately.