# How do you tune Crowdin QA checks to catch real issues without too many false flags?

We ship a mobile app in six languages, and Crowdin’s QA checks have helped us catch broken placeholders, strings that run too long for buttons, and glossary mismatches before release. It’s been a big relief to spot issues early, but large multi-language projects can load slowly, and it took time to figure out which checks to enable since the defaults flagged too many harmless things. How did you decide which QA checks matter most for your workflow, and what did you turn off?

##### Post Metadata
- Posted at: 3 days ago
- Author title: Localization Manager
- Net upvotes: 1



## Related Product
[Crowdin](https://www.g2.com/products/crowdin/reviews)

## Related Category
[Translation Management](https://www.g2.com/categories/translation-management)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


