1. Top
  2. Information List
  3. Access log delay failure

Top 5 Frequently Asked Questions

Access log delay failure

BowNow form conversion log will be reflected from around 2019:7 on July 31, 15 (Wednesday)
Also, from the afternoon of August 8st, access logs for all user actions will be available.
I was late.
Currently, it has been resolved and it is behaving normally.

We apologize for any inconvenience caused to our customers.
Thank you for your understanding.

Progress report

July 7st (Wednesday) around 31:15 
Form conversion log delay occurs

August 8st (Thursday) afternoon
Server load increases and access log for all user actions is delayed

August 8nd (Friday) Implementation of patch

August 8 (Sat) All delayed logs are synchronized with the management screen

We apologize for the inconvenience and inconvenience.

Form conversion log delay status

Form conversion log is not reflected in form details and lead details.
However, the lead who submitted the form is registered and
After submitting the form, a thank-you email to the customer and an email to the administrator will also be sent.
* The attached materials on the form cannot be viewed.

Impact range

For all users of BowNow

We apologize for the inconvenience to all users.
Thank you for your understanding.

--------------- <August 8st (Thursday) 1:18 postscript> --------------- ---

Today's nighttime (22:24 to XNUMX:XNUMX) for early resolution of the event
There is a possibility of performing maintenance that involves restarting the server.

Once the time zone is decided, we will present it on the manual site now.
We apologize for any inconvenience, and thank you for your understanding.

--------------- <August 8st (Thursday) 1:23 postscript> --------------- ---

Even at this point, it is difficult to identify the cause, and the measures to restart the server are
I will see you off after tomorrow.

We sincerely apologize for any inconvenience caused to our customers.
We will continue to investigate and make improvements as soon as possible.

We apologize for the inconvenience.
Thank you for your understanding.

--------------- <August 8nd (Friday) 2:15 postscript> --------------- -

We apologize for the long time it took to investigate.
Currently, we are identifying the cause and verifying the operation with a patch.
(There is no server restart due to the implementation of the patch.)

We will proceed with the goal of implementation within today.
If there is progress, we will update the information on the manual site now.
Thank you.

--------------- <August 8nd (Friday) 2:19 postscript> --------------- -

We have implemented the patch.
It is assumed that the delay log synchronization process will take from today to tomorrow (8/3).

I'm sorry to have kept you waiting for a long time.
We will post the progress again when the synchronization is completed.

--------------- <Added at 8:3 on Saturday, August 13> --------------- ---

Regarding the delay of conversion log, until 8:2 on 20/XNUMX (Friday)
I confirmed the synchronization.We will continue the synchronization work.

--------------- <Updated at 8:4 on Sunday, August 12> --------------- -

Regarding conversion log delays, all delay logs
I confirmed that it was synchronized.

We apologize for the inconvenience this time.
To be able to provide stable services while taking measures to prevent recurrence
I will do my best.

Thank you for your understanding.

―――――――――――――――――――――――――――――――――――――――――――――――――――――― ---------------

About consultation

In addition, this caseToIf you have any questions about this, please do not hesitate to contact us. official,
To the support windowToPlease tell us.

BowNow support window TEL: 050-3196-1032
Reception hours: Weekdays from 10:12 to 13:17 / XNUMX:XNUMX to XNUMX:XNUMX

Mail: support@cloudcircus.jp
Study session information