API "build" logic

[PierreSchwang]

@Tania

Regarding your question about the build project not always starting a new build, the logic is that the system cannot initiate a new build until the previous one has finished. This is to prevent parallel builds, which are not allowed. If you’re trying to force a build, it’s not possible directly, but you can check the status of the latest build using the API endpoint provided in previous communications.

Hi, could you further elaborate on that? I’m trying to POST to https://<organization>.crowdin.com/api/v2/projects/<projectId>/translations/builds to trigger a fresh build. The API returns a 201 CREATED but returns a build from yesterday while not creating a new one. Maybe no new build is being made, because there hasn’t been any new translations - but the status code would be kinda misleading while not stating any further information on why. My main issue is, that I’m specifying new parameters to the request (?exportApprovedOnly=true&skipUntranslatedFiles=true) - which should trigger a new build as the previous build does contain non-approved strings - but just doesn’t. I have no way to force that in whatever way. I wanted to try if Export ignores setting to export only approved translations - #2 by Natalia fixes my issue as simply specifying exportApprovedOnly did not seem to work - but literally can’t.