How to handle asynchronous queue errors?
This is it, we have made a public account tool. User group A has the ability to send template messages in groups, and user group B can receive template messages.
After user A fills in the content on the page and submits it, because it is sent in bulk, it may take a very long time, so we implement asynchronous processing and push all the user's messages into a queue. If the push is successful, it will be returned to the user. A is successful. User A's front-end operation is over.
After that, the background will scan the queue every period of time. If there is data in the queue, mass push will be performed.
Now there is such a problem. Uncertain factors begin to appear on the official account (sometimes api changes, sometimes server 50X errors), which causes queue push on my side to begin to fail. Fortunately, network timeouts or temporary errors can be solved with scheduled retries.
But if the server API is replaced like this, our push will fail 100%, and user group B will never receive the message. However, this error will not be seen by user A, who will think that the message was sent successfully. (Because it has been changed to asynchronous, the push ends when it is queued, and you cannot keep staring at this big push list. It may take a very long time)
So I would like to ask if there is any design solution that can make user A aware that there is a problem with the official account server when there is a problem with the official account api server.
I have considered exposing the status of the push list to user A. User A can see the status of the push by himself. However, it doesn't feel intuitive, and user A may not look at this list.
Reply content:
This is it, we have made a public account tool. User group A has the ability to send template messages in groups, and user group B can receive template messages.
After user A fills in the content on the page and submits it, because it is sent in bulk, it may take a very long time, so we implement asynchronous processing and push all the user's messages into a queue. If the push is successful, it will be returned to the user. A is successful. User A's front-end operation is over.
After that, the background will scan the queue every period of time. If there is data in the queue, mass push will be performed.
Now there is such a problem. Uncertain factors begin to appear on the official account (sometimes api changes, sometimes server 50X errors), which causes queue push on my side to begin to fail. Fortunately, network timeouts or temporary errors can be solved with scheduled retries.
But if the server API is replaced like this, our push will fail 100%, and user group B will never receive the message. However, this error will not be seen by user A, who will think that the message was sent successfully. (Because it has been changed to asynchronous, the push ends when it is queued, and you cannot keep staring at this big push list. It may take a very long time)
So I would like to ask if there is any design solution that can make user A aware that there is a problem with the official account server when there is a problem with the official account api server.
I have considered exposing the status of the push list to user A. User A can see the status of the push by himself. However, it doesn't feel intuitive, and user A may not look at this list.
Isn’t this solution unreasonable? Even if user A gets the exception information, you are still the one who handles the problem. What’s the point of giving him an error? Why do I think you should solve the problem of the server api first? The key is
Write error logs.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











This tutorial demonstrates how to efficiently process XML documents using PHP. XML (eXtensible Markup Language) is a versatile text-based markup language designed for both human readability and machine parsing. It's commonly used for data storage an

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

A string is a sequence of characters, including letters, numbers, and symbols. This tutorial will learn how to calculate the number of vowels in a given string in PHP using different methods. The vowels in English are a, e, i, o, u, and they can be uppercase or lowercase. What is a vowel? Vowels are alphabetic characters that represent a specific pronunciation. There are five vowels in English, including uppercase and lowercase: a, e, i, o, u Example 1 Input: String = "Tutorialspoint" Output: 6 explain The vowels in the string "Tutorialspoint" are u, o, i, a, o, i. There are 6 yuan in total

What are the magic methods of PHP? PHP's magic methods include: 1.\_\_construct, used to initialize objects; 2.\_\_destruct, used to clean up resources; 3.\_\_call, handle non-existent method calls; 4.\_\_get, implement dynamic attribute access; 5.\_\_set, implement dynamic attribute settings. These methods are automatically called in certain situations, improving code flexibility and efficiency.

PHP and Python each have their own advantages, and choose according to project requirements. 1.PHP is suitable for web development, especially for rapid development and maintenance of websites. 2. Python is suitable for data science, machine learning and artificial intelligence, with concise syntax and suitable for beginners.

PHP is widely used in e-commerce, content management systems and API development. 1) E-commerce: used for shopping cart function and payment processing. 2) Content management system: used for dynamic content generation and user management. 3) API development: used for RESTful API development and API security. Through performance optimization and best practices, the efficiency and maintainability of PHP applications are improved.

PHP is a scripting language widely used on the server side, especially suitable for web development. 1.PHP can embed HTML, process HTTP requests and responses, and supports a variety of databases. 2.PHP is used to generate dynamic web content, process form data, access databases, etc., with strong community support and open source resources. 3. PHP is an interpreted language, and the execution process includes lexical analysis, grammatical analysis, compilation and execution. 4.PHP can be combined with MySQL for advanced applications such as user registration systems. 5. When debugging PHP, you can use functions such as error_reporting() and var_dump(). 6. Optimize PHP code to use caching mechanisms, optimize database queries and use built-in functions. 7
