Error message during a PDM dispatch: Unable to label a folder

Hi all

I get from time to time an error message (see screenshot) when changing the status in pdm.
This change of state launches a dispatch and sends me this message which does not really enlighten me on the reasons for the latter.
Everything seems to be working well and the appearance of this message seems random.

Do you have any idea what this message means?

image

Thank you.

Hello
It all depends on what the dispatch script is supposed to do. With so little information, you can't really help.
Is there any manipulation of the file? If so, does this massage happen when you transition from SW or is the file open in SW and you transition in the explorer?

As for the change of state launched from PDM or SW, I asked the users to find out what it is.

The dispatch that is launched during this change of state does not act directly on the file in question. Indeed, the change of state of the file launches a task that generates a pdf of the file.
It is the creation of this file that will launch a dispatch.

This dispatch will actually act on the pdf and not the first file on which the change of state is made.

I didn't describe this principle too much because I thought there was a clear meaning behind this message (like the file doesn't exist or related to a legal problem)

Quite honestly, "impossible to label the file" is not telling no.
Either a dubious translation from English or a bug.
All I can say is that the dispatch script even to make a PDF, will open the file in SW then generate the export and then close.
I've never tested with a file already open in SW but possible that it will crash (two SW sessions with the same file open).
Other dispatch actions, such as checkout, cannot be done if the file is open in SW and requires working only in the explorer.
If you think it's a legal problem, in this case you have to check in which folder the script generates the PDF and check that users have write rights to this folder.

What is surprising is that in the end it works as a general rule and from time to time users get this error message.
I'll dig into that, thank you very much.