Where do I report bugs?

Report bugs by opening an issue on our GitHub repository at github.com/apifyforge/apifyforge. We use GitHub Issues as our primary bug tracking system because it allows public visibility, threaded discussions, and status tracking for every reported issue. To help us diagnose and fix your bug quickly, include the following information in your report. The error message — copy the exact error text, including any error codes or stack traces. What you were doing — describe the steps that led to the bug, step by step, so we can reproduce it. Which tool or dashboard page was involved — specify whether the issue is in the Schema Validator, Test Runner, Cloud Staging, fleet dashboard, revenue tracker, quality score page, or another feature. Browser information — include your browser name and version (e.g., Chrome 120, Firefox 115, Safari 17) and your operating system. Screenshots — visual evidence of the bug is extremely helpful, especially for layout issues, incorrect data displays, or error dialogs. Browser console output — if applicable, open your browser's developer tools (F12), go to the Console tab, and copy any error messages shown there. For tool-specific bugs, include additional details. For Schema Validator issues: the actor name, the content of your dataset_schema.json, a sample of your actor's output, and the full validator error output. For Test Runner issues: the actor name, the test case configuration you used, and the complete test output including any assertion failures. For Cloud Staging issues: the actor name, the build version tested, and the staging report output. For dashboard and analytics issues: whether the data appears incorrect (and what the correct value should be), whether the page fails to load entirely, or whether specific metrics are missing. We triage new issues daily and typically respond within 24 hours. Bug priority is based on impact: issues affecting data accuracy (incorrect revenue figures, wrong success rates), tool functionality (validator crashes, test runner failures), and security concerns are addressed first. Feature requests are welcome but tracked separately from bugs. If your issue is urgent — for example, revenue tracking shows incorrect data that is affecting business decisions — mention 'urgent' in the issue title and we will prioritize it. For general questions that are not bugs, check the other FAQ answers on this page first, as many common questions are already answered. For related information, see the questions about how to connect your account and troubleshooting empty dashboards.