How to troubleshoot WeChat alarms in PHP Development

Scenario. Currently, the number of users is more than million, and the number of daily active users is about 30-40 million (may not be accurate ~) In this scenario, most alarms are reported by geographic locations. Currently, geographic location reports use the following solution: users report geographical locations by longitude and latitude through Baidu.

Currently, the number of users is about million, and the number of daily active users is about 30-40 million (which may be inaccurate ~) Left and right.

In this scenario, most alarms are reported by geographic locations. Currently, the following solutions are used for geographic location reporting:

The user reports the geographical location and writes it to the redis set after obtaining the user's current City Based on the latitude and longitude, run scripts in the background to update user data to the mysql database (here LZ feels there is no need to update data to mysql, ....)

The problem is that an alarm is often reported for a geographical location and is not returned within 5 seconds. Of course, an alarm is reported for a geographical location alarm only when scanning the QR code to cancel the attention and other events.

Would you like to ask if you have similar experience and have better troubleshooting and solutions for such alarms?

Reply content:

Scenario.

Currently, the number of users is about million, and the number of daily active users is about 30-40 million (which may be inaccurate ~) Left and right.

In this scenario, most alarms are reported by geographic locations. Currently, the following solutions are used for geographic location reporting:

The user reports the geographical location and writes it to the redis set after obtaining the user's current City Based on the latitude and longitude, run scripts in the background to update user data to the mysql database (here LZ feels there is no need to update data to mysql, ....)

The problem is that an alarm is often reported for a geographical location and is not returned within 5 seconds. Of course, an alarm is reported for a geographical location alarm only when scanning the QR code to cancel the attention and other events.

Would you like to ask if you have similar experience and have better troubleshooting and solutions for such alarms?

The public account has the permission to send messages.
The authentication service number has the permissions of the customer service message interface and template message interface. The authenticated subscription number does not have the template message interface permission.

After receiving the user message, you can reply to only one prompt message, such as "processing, please wait". After the program is processed, it is sent to the user through the customer service message interface.

In addition, it will be repeated twice after 5S failure. You can compare the msgid for reply processing.