* 12:00 May 31, 2022　　- The content has been updated.

We would like to report the cause and future response policy for the search-related failure that occurred on May 26, 2022.

■ Failure details
– Files may not be searched by Fleekdrive

■ Cause
Because there were many requests and the registration process took a long time in Full-text search.
In addition, the time required to register the Full-text search affected the Normal search,
which delayed the process and caused the event that the search could not be performed.

■ The response policy
We are considering improving the database queries related to Full-text search and taking measures so that the registration process does not take time.

——————————–＜past reports (as of 10:20, May 27)＞————————————
We have confirmed the occurrence of the following events on Fleekdrive, but we are pleased to inform you that all of them have now been resolved.

■ Failure details
– Files may not be searched by Fleekdrive

■ Time of failure occurrence – GMT+9 Japan time
Normal search : May 26, 2022, around 09:10 to 11:50
Full-text search : May 26, 2022, around 09:50 to May 27, 2022, around 06:10

■ Cause and current status
The cause is still under investigation.

The search function is executed by batch processing, but since it was confirmed that there was a delay in batch processing, the batch server was restarted.
As a result, it was confirmed that the Normal search was resolved and all the processing in the Full-text search was completed around 06:10 on May 27, 2022.

We apologize for the inconvenience and appreciate your continued support.

——————————–＜past reports (as of 16:30, May 26)＞————————————
We have confirmed the occurrence of the following events on Fleekdrive, but we will continue to support Full-text search (search in files).

■ Failure details
– Files may not be searched by Fleekdrive

■ Time of failure occurrence – GMT+9 Japan time
Normal search : May 26, 2022, around 09:10 to 11:50
Full-text search : May 26, 2022, around 09:50 to *currently the failure is still occurring

■ Cause and current status
The cause is still under investigation.

The search function is executed by batch processing, but since it was confirmed that there was a delay in batch processing, the batch server was restarted.
As a result, the normal search’s event has been resolved, and the processing for Full-text search is gradually being executed,
but all the Full-text search have not been resolved yet.

——————————–＜past reports (as of 13:30, May 26)＞————————————
We have confirmed the occurrence of the following events on Fleekdrive,
but we would like to report that the issues have been resolved for Normal search (file / space name search).
Full-text search will continue to be supported.

■ Failure details
– Files may not be searched by Fleekdrive

■ Time of failure occurrence – GMT+9 Japan time
Normal search : May 26, 2022, around 09:10 to 11:50
Full-text search : May 26, 2022, around 09:50 to *currently the failure is still occurring

■ Cause and current status
We are currently investigating with the highest priority.

——————————–＜past reports (as of 12:00, May 26)＞————————————
We are pleased to inform you that we have confirmed that the following issue may occur in Fleekdrive.

■ Time of failure occurrence – GMT+9 Japan time
– May 26, 2022
*the incident time is still investigating and currently the failure is still occurring

■ Failure details
– files may not be searched

■ Cause and current status
We are currently investigating with the highest priority.

We will make a follow-up announcement when the issue is solved.
We apologize for the inconvenience and appreciate your continued support.