Hi Evgenii Samarin ,

Regarding messages that are display in the UI:

• The platform called your extension’s /v1/bcmtranslate and received HTTP 400:
    ERROR - The POST request sent to https://…/v1/bcmtranslate failed with status code 400
• Because the response body wasn’t a recognized error model, LC recorded:
    TaskError(name=processTask, code=FileProcessingException, value=Unknown error)

Things to check:

Use the blueprint exceptions and middleware (recommended)
- If you’re using our app blueprint, add the exception middleware and throw our AppException types (they set both the HTTP status code and the JSON error body in the format LC expects). See existing exceptions managed from the Blueprint that you can use or extend here: https://github.com/RWS/language-cloud-extensibility/tree/cdc8552e3c22392adf8039d8f2378a69737b2e9e/blueprints/dotNetAppBlueprint/Rws.LC.AppBlueprint/Exceptions

However, I'm also seeing a 'Invalid tenantId provided' message from the logs associated with yr trace-id.  This could indicate that the request/engine is being resolved against a tenant where the extension isn’t installed or no longer matches current config.

Potential causes:

• maybe the extension base URL changed
• the engine/route belongs to a different organization/tenant
• extension was removed/reinstalled and the engine/route references changed?

Recommend:

• Check that your add-on is installed in the tenant correctly and that the workflow template correctly represents the latest version.

Hi Evgenii Samarin ,

Regarding messages that are display in the UI:

• The platform called your extension’s /v1/bcmtranslate and received HTTP 400:
    ERROR - The POST request sent to https://…/v1/bcmtranslate failed with status code 400
• Because the response body wasn’t a recognized error model, LC recorded:
    TaskError(name=processTask, code=FileProcessingException, value=Unknown error)

Things to check:

Use the blueprint exceptions and middleware (recommended)
- If you’re using our app blueprint, add the exception middleware and throw our AppException types (they set both the HTTP status code and the JSON error body in the format LC expects). See existing exceptions managed from the Blueprint that you can use or extend here: https://github.com/RWS/language-cloud-extensibility/tree/cdc8552e3c22392adf8039d8f2378a69737b2e9e/blueprints/dotNetAppBlueprint/Rws.LC.AppBlueprint/Exceptions

However, I'm also seeing a 'Invalid tenantId provided' message from the logs associated with yr trace-id.  This could indicate that the request/engine is being resolved against a tenant where the extension isn’t installed or no longer matches current config.

Potential causes:

• maybe the extension base URL changed
• the engine/route belongs to a different organization/tenant
• extension was removed/reinstalled and the engine/route references changed?

Recommend:

• Check that your add-on is installed in the tenant correctly and that the workflow template correctly represents the latest version.