(Updated on 2025-09-17 at 15:01 (JST))
When we reported the issue, we stated that only the asynchronous HTTP interface v1 was affected, but we have added this information because v2 was also affected.

(Published on 2025-09-17 at 14:23 (JST))
Normally, the company is using the いただき, and the sincere にありがとうございます.

As described below, there was an issue where job processing failed in the asynchronous HTTP interface (v1/v2). This issue has now been resolved. We sincerely apologize to our customers for any inconvenience caused.

◆ Scope of impact
Period of occurrence: Wednesday, September 17, 2025, 12:08 - 14:05
Target service: Asynchronous HTTP interface v1/v2

◆Phenomenon
During the above time period, all jobs were failing. When trying to retrieve the results, the following response was returned:

{"status":"error","session_id":"0199560991b20a306b8f9c99","service_id":"userX","error_message":"ERROR: Failed to copy engine mode - 0"}

◆Cause
Due to the maintenance work carried out on the same day, the necessary resource files could not be obtained from the container that processes the interface.

◆ Request to customers
We apologize for the inconvenience, but for any jobs that failed during this period, please create the job and run it again. There will be no charge for failed jobs.

We deeply apologize for the inconvenience caused.