Hi Zhenya Mamenko , it is what it says in the message. The token yr using to call the endpoint probably does’not belong to the same service user that owns the task. The API is preventing the user from accessing task scoped artifacts (like target file versions) when the authenticated service user differrs from the task’s service user owner.

To fix, you'd need to make sure the workflow’s automatic step that creates ‘n runs the task is configured to ‘Run as’ the same service user as your connector (the same clientId you use to obtain the token).

Please also make reference to this page detailing how to report an issue, so that we can provide better support.

Hi Zhenya Mamenko , it is what it says in the message. The token yr using to call the endpoint probably does’not belong to the same service user that owns the task. The API is preventing the user from accessing task scoped artifacts (like target file versions) when the authenticated service user differrs from the task’s service user owner.

To fix, you'd need to make sure the workflow’s automatic step that creates ‘n runs the task is configured to ‘Run as’ the same service user as your connector (the same clientId you use to obtain the token).

Please also make reference to this page detailing how to report an issue, so that we can provide better support.

Patrick Andrew Hartnett 

Hello Patrick! We've encountered another issue - after the upload of bcm document, the editor is not opening we don't have access to any error message, all we can see is error message and infinite loading of the segment editor:

Evgenii Samarin 

What happens if you click on this:

Does it provide you with the details, including the trace id?

Hi Paul! There's no event on click

Hi Evgenii Samarin , Are you able to access the notifications from the main window, after you close the editor view?

Example:

Can you provide more context, steps to reproduce, content, filetype, source file etc...?

Important: If this issue is not related to the initial reason for creating this post 'An error while trying to make a "POST" REQUEST at Url:...' then I'd recommend you keep them separate for auditing so that we can track them better and ensure the right team is involved when following up.