We are configuring jobs from the API. 

We are using HTTP for job input.

For example, when we provide a file named “xxxxxxx_xxxxxxxx_xxxx_xxxxxxxxx.#revxxxxxxxxxxxxxx#.mp4” as job input, the job causes an error. 

The specific error details are as follows:

----------- highlevel.log -----------

2024-09-09T09:02:21.498Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:03:09.994Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:03:58.742Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:04:47.949Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:05:37.285Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:06:24.433Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:07:11.543Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:07:58.661Z error [OUTPUT] http error 409 - Conflict

2024-09-09T09:07:58.661Z error [GENERAL] Output xxxxxxx_xxxxxxxx_xxxx_xxxxxxxxx.# failure: i/o error

--------------------------------------

However, this error does not occur with the following file name:

“xxxxxxxx_xxxxxxxx_xxxx_xxxxxxxxx.#revxxxxxxxxxxxxxx#.mp4” (the position of the first “#” is at the 33rd character)

When the asset file name is determined, the first 32 characters of the input file name are adopted as the base name. 

Therefore, this issue seems to occur only when “#” is included within the first 32 characters of the input file name.

Is this intended behavior?