Work order exception processing method and device, server and storage medium

Abstract

The application provides a work order exception processing method and device, a server and a storage medium. The method comprises the following steps: after obtaining a work order, the server creates work order resources one by one according to the work order. When an exception occurs in the creation of a work order resource, the server publishes a processing exception event. According to the work order number, the server queries the work order resources that have been successfully created in the resource list, and counts the number of the work order resources. When the number of the work order resources is greater than or equal to 1, the server modifies the state of the work order in the work order list to be cleaned up. According to the resource list, the server deletes the work order resources. When the number of the work order resources is 0, the server modifies the state of the work order in the work order list to be retried. The server also re-creates the work order resources of the work order. The method of the application realizes the deletion and release of the resources in the instance of the work order, and improves the resource utilization.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, device, server, and storage medium for handling work order exceptions. Background Art

[0002] With the development of cloud computing, customers have increasingly high requirements for the accuracy of cloud product activation. Among them, customers are most concerned about whether the instance to be created in the work order can be correctly activated.

[0003] In the prior art, when an exception occurs in an instance to be created in a work order, an exception closed loop can realize the throwing and monitoring of the exception, and restore the environment variables before the exception by rolling back the stack.

[0004] However, when processing created instances through stack rollback, there is a low resource release rate, which easily leads to resource waste. Summary of the Invention

[0005] The present application provides a work order exception handling method, device, server and storage medium to solve the technical problem of low resource release efficiency of created exception instances in the prior art, which leads to resource waste.

[0006] In a first aspect, the present application provides a method for handling work order exceptions, comprising:

[0007] When a resource creation exception occurs for a work order, an exception handling event is published and the work order resources and resource quantity of the work order resources that have been successfully created are obtained from the resource list.

[0008] When the number of resources is greater than or equal to 1, the work order status in the work order list is changed to pending cleanup, and the work order resources are deleted according to the resource list;

[0009] When the number of resources is 0, the work order status in the work order list is changed to pending retry, and the work order resources of the work order are recreated.

[0010] Optionally, delete the work order resources based on the resource list, including:

[0011] Publish the "Start Cleanup" event and change the status of the work order in the work order list to "Cleanup in Progress";

[0012] For each work order resource, a resource cleanup event is published and the record corresponding to the resource number of the work order resource is deleted.

[0013] Optionally, the method further includes:

[0014] When all the work order resources of the work order in the resource list are deleted successfully, a cleanup success event is published and the work order status in the work order list is changed to pending restart.

[0015] When the deletion of a work order resource with a work order in the resource list fails, a cleanup failure event is published and the work order status in the work order list is changed to cleanup failure.

[0016] Optionally, before obtaining the resource for which the work order has been successfully created from the resource list, the method further includes:

[0017] Get the work order, publish the start processing event, save the work order information to the work order list, and change the work order status in the work order list to executing;

[0018] Create work order resources for each work order one by one according to the work order. When each work order resource is successfully created, publish a resource creation event and store the work order information and resource information of the work order in the resource list.

[0019] The work order information at least includes the work order number, and the resource information at least includes the resource number.

[0020] Optionally, create work order resources for each work order, including:

[0021] Determine the creation method of each work order resource based on the code arrangement, which includes synchronous creation and asynchronous creation.

[0022] According to the creation method of the work order resource, call the corresponding interface of the work order resource to create the work order resource;

[0023] Get the creation result of each work order resource, where the creation result includes creation success and creation failure.

[0024] Optionally, the method further includes:

[0025] When all the work order resources of the work order are created successfully, a processing success event is published and the work order status in the work order list is changed to success.

[0026] Optionally, before modifying the work order status of the work order list, the method further includes:

[0027] Query and verify the current status of the work order.

[0028] In a second aspect, the present application provides a work order exception handling device, comprising:

[0029] The acquisition module is used to publish and handle exception events when a work order resource creation exception occurs, and obtain the work order resources that have been successfully created and the resource quantity of the work order resources from the resource list;

[0030] The processing module is used to change the work order status in the work order list to pending cleanup when the number of resources is greater than or equal to 1, and delete the work order resources according to the resource list; when the number of resources is 0, change the work order status in the work order list to pending retry and recreate the resources of the work order.

[0031] Optionally, the processing module is specifically configured to:

[0032] Publish the "Start Cleanup" event and change the status of the work order in the work order list to "Cleanup in Progress";

[0033] For each work order resource, a resource cleanup event is published and the record corresponding to the resource number of the work order resource is deleted.

[0034] Optionally, the processing module is further configured to:

[0035] When all work order resources in the resource list are deleted successfully, a cleanup success event is published, and the work order status in the work order list is changed to pending restart.

[0036] When the deletion of a work order resource in the resource list fails, a cleanup failure event is published and the work order status in the work order list is changed to cleanup failure.

[0037] Optionally, the processing module is further configured to:

[0038] Get the work order, publish the start processing event, save the work order information to the work order list, and change the work order status in the work order list to executing;

[0039] Create work order resources for each work order one by one according to the work order. When each work order resource is successfully created, publish a resource creation event and store the work order information and resource information of the work order in the resource list.

[0040] The work order information at least includes the work order number, and the resource information at least includes the resource number.

[0041] Optionally, the processing module is specifically configured to:

[0042] Determine the creation method of each work order resource based on the code arrangement, which includes synchronous creation and asynchronous creation.

[0043] According to the creation method of the work order resource, call the corresponding interface of the work order resource to create the work order resource.

[0044] Optionally, the processing module is further configured to:

[0045] When all the work order resources of the work order are created successfully, a processing success event is published and the work order status in the work order list is changed to success.

[0046] Optionally, before modifying the work order status of the work order list, the method further includes:

[0047] Query and verify the current status of the work order.

[0048] In a third aspect, the present application provides a server, comprising: a processor, and a memory communicatively connected to the processor;

[0049] The memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method in the first aspect and any possible design of the first aspect.

[0050] In a fourth aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When the computer-executable instructions are executed by a processor, they are used to implement the method in the first aspect and any possible design of the first aspect.

[0051] The work order exception handling method, device, server and storage medium provided in the present application create work order resources one by one according to the work order after obtaining the work order; when a work order resource creation exception occurs, publish a handling exception event; according to the work order number, query the work order resources that have been successfully created for the work order in the resource list, and count the resource quantity of the work order resources; when the resource quantity is greater than or equal to 1, change the work order status in the work order list to pending cleanup; delete the work order resources according to the resource list; when the resource quantity is 0, change the work order status in the work order list to pending retry; and recreate the work order resources of the work order to improve resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0053] Figure 1 A schematic diagram of a work order service scenario provided in one embodiment of the present application;

[0054] Figure 2 A flowchart of a method for handling work order exceptions provided in one embodiment of the present application;

[0055] Figure 3 An example of handling work order exceptions provided in one embodiment of the present application;

[0056] Figure 4 A flowchart of a method for handling work order exceptions provided in one embodiment of the present application;

[0057] Figure 5 An example of handling work order exceptions provided in one embodiment of the present application;

[0058] Figure 6 FIG. 1 is a structural schematic diagram of a work order exception processing device according to an embodiment of the present application;

[0059] Figure 7 FIG. 2 is a hardware structural schematic diagram of a server according to an embodiment of the present application.

[0060] The specific embodiments of the present application have been shown in the above-described drawings, and will be described in more detail hereinafter. These drawings and the following description are not intended to limit the scope of the present application in any way, but to explain the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0061] The exemplary embodiments will be described in detail herein below with reference to the drawings. In the following description, the same drawings refer to the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application as detailed in the appended claims.

[0062] During the execution of a program, if an exception occurs in one of the steps, the overall process will fail. The exception closed loop refers to the recovery of the program operation before the step where the exception occurs, the exception prompt, and the re-operation after the exception is repaired. Currently, the common way is to throw an exception during program execution and to monitor the program in real time. The server can be set with a threshold value. When the monitoring value exceeds the threshold value, it can be determined as a fault and an alarm is processed.

[0063] With the development of the cloud computing industry, customers have increasingly high requirements for the accuracy of cloud product opening. Among them, the customer is most concerned about whether the instance to be created in the work order can be correctly opened. In order to ensure the correct execution of the customer's work order, the existing technology introduces an exception closed loop process. At present, the main function of the exception closed loop is to realize the throwing of exceptions, real-time monitoring, setting threshold values, alarm processing, etc. In addition, the existing exception closed loop can also realize the rollback of the stack through the principle of virtual machine.

[0064] In the prior art, the main concern of the exception closed loop is to discover exceptions and recover from exceptions. The prior art realizes the prompt of the operation and maintenance personnel to timely locate the problem through the alarm after discovering the exception, thereby improving the user experience. The prior art can also recover from exceptions through rollback. However, the prior art mainly focuses on the recovery of environmental variables, and rarely focuses on how to recycle the instance that has been created before the exception occurs. Especially for cloud computing related products, both customers and suppliers are more concerned about the creation of instance resources than the release of abnormal instance resources.

[0065] To address the above technical issues, embodiments of the present application provide a method for handling work order exceptions. This method describes in detail how to reclaim instances created in a previous process after an exception is discovered. This process primarily includes two steps: publishing an exception instance orchestration and clearing an exception instance orchestration. This method reduces the occurrence of unknown instances and resource space usage. The process of publishing the exception instance orchestration primarily involves publishing four events: a start processing event after obtaining a work order; a resource creation event after each resource is created; a handle exception event if an exception occurs during resource creation; and a handle success event after all resources in the work order are successfully created. After publishing the handle exception event, the server needs to clear the already created exception instances. This process is referred to as exception instance orchestration. This process primarily involves publishing four events: a start cleanup event; a resource cleanup event if already created resources exist; a cleanup success event if the work order's resources are successfully deleted; and a cleanup failure event if the work order's resources fail to be deleted.

[0066] The following describes exemplary application scenarios of the embodiments of the present application.

[0067] Figure 1 A schematic diagram of a work order service scenario provided by an embodiment of the present application is shown. Figure 1 As shown, a user can send a work order request to the server through a user terminal. Upon receiving the work order request, the server can create an instance of the work order. Each instance is equivalent to a work order resource. When all instances of the work order are created, the server can notify the user of the success.

[0068] In this application, the server is used as the execution entity to execute the work order exception handling method of the following embodiment. Specifically, the execution entity can be a hardware device of the server, or a software application that implements the following embodiment in the server, or a computer-readable storage medium that has installed thereon the software application that implements the following embodiment, or the code that implements the software application of the following embodiment.

[0069] The following specific embodiments are used to describe the technical solution of the present application in detail. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0070] Figure 2 A flowchart of a work order exception handling method provided by an embodiment of the present application is shown. Figure 1 Based on the embodiment shown, Figure 2 As shown, with the server as the execution subject, the method of this embodiment may include the following steps:

[0071] S101. When a work order resource creation exception occurs, publish a processing exception event, and obtain the work order resources for which the work order has been successfully created and the resource quantity of the work order resources that have been successfully created from the resource list.

[0072] In this embodiment, after obtaining the work order, the server can create work order resources one by one according to the work order. When a work order resource creation exception occurs, the server can publish a processing exception event. Optionally, the work order resource creation exception includes at least the failure to create the work order resource. Optionally, the work order resource creation exception may also include the work order resource creation time exceeding a threshold. Optionally, the work order resource creation exception may also include the abnormality of the parameters in the creation process of the work order resource. The server can determine the work order number of the current work order through the work order list. The server can query the work order resources that have been successfully created for the work order in the resource list based on the work order number. The resource list is used to record the work order resources that have been successfully created for the work order. The server can obtain the work order resources that have been successfully created for the work order from the resource list. The server can also obtain the resource quantity of the work order resources that have been successfully created for the work order from the resource list.

[0073] Optionally, the server issues a processing exception event to notify the technician of a work order creation failure. The technician can view the work order list on a display page and identify the work order with the exception. Optionally, the display page may also include a cleanup button. Optionally, the cleanup button allows the technician to initiate the deletion and release of work order resources for the failed work orders. When the user clicks the cleanup button, the server may begin cleaning up the work order resources for the failed work orders. Optionally, the work order list display page may include a first number of work orders. The first number of work orders may include a second number of failed work orders, where the second number is less than or equal to the first number. The first and second numbers are set solely to distinguish the two work orders. Optionally, the technician can directly click the cleanup button. The server will sequentially delete and release the work order resources for the second number of failed work orders. Optionally, the technician can select some or all of the second number of work orders and then click the cleanup button. The server will sequentially delete and release the work order resources for the selected failed work orders. Optionally, the server may sequentially obtain the work orders that failed to be created according to the order of the work orders in the work order list, and process the work orders that failed to be created one by one.

[0074] Optionally, when the server obtains a work order that failed to be created, the server can store the work order number of the work order in a thread variable (ThreadLocal), so that the thread corresponding to the work order number is the current thread. Optionally, when the thread corresponding to the work order is the current thread, the server queries the resource list for the work order resources that have been successfully created for the work order and the resource quantity of the work order resources.

[0075] Optionally, when the work order resource has not been cleared, the status of the work order resource in the work order list may be success. Optionally, when the server counts the work order resources of the work order, the work order resources with a status of success may be counted.

[0076] S102. When the number of resources is greater than or equal to 1, the work order status in the work order list is changed to pending cleanup, and the work order resources are deleted according to the resource list.

[0077] In this embodiment, the server can determine whether the number of resources is greater than or equal to 1. When the number of resources is greater than or equal to 1, it means that at least one work order resource of the work order has been successfully created. The server needs to delete these work order resources to release the resources of the instance where the creation failed. When it is determined that there are work order resources that have been successfully created, the server can modify the work order status in the work order list to be cleaned up. The to-be-cleaned status is used to indicate that there is at least one work order resource in the work order that failed to be created that needs to be cleaned up. The server can delete the work order resources corresponding to the work order one by one according to the resource list. Optionally, the work order status can be a column in the work order list.

[0078] In one example, the specific process of deleting a work order resource may include:

[0079] Step 1: Publish the start cleanup event and change the work order status in the work order list to cleanup in progress.

[0080] In this step, the server can publish a "Start Cleanup" event and change the status of the work order in the work order list to "Cleanup in Progress".

[0081] Step 2: For each work order resource, publish a resource cleanup event and delete the record corresponding to the resource number of the work order resource.

[0082] In this step, the server can sequentially obtain the work order resources of the work order from the resource list. After the server obtains a work order resource, the server can publish a resource cleanup event for the work order resource. Optionally, the server can obtain the work order resource from the resource list, and specifically obtain the resource number of the work order resource. Optionally, in order to distinguish the resource cleanup events of different work order resources, the resource cleanup event can include the resource number of the cleaned work order resource. The server can delete the work order resource by deleting the record corresponding to the resource number of the work order resource. Optionally, the server can also delete the work order resource by releasing the resource. For example, when the resource is a bandwidth resource, the server can delete the work order resource by releasing the bandwidth resource. After the deletion of the work order resource is completed, the bandwidth resource can be obtained by other instances. The other instance can be an instance of another work order. Alternatively, the other instance can also be another instance of the work order.

[0083] Optionally, when a work order resource is deleted, the server may record the work order resource's status as deleted in the resource list. Optionally, when a work order resource is cleared but the clearing fails, the server may record the work order resource's status as failed in the resource list. Optionally, when the work order resource's status is failed, the server may also record the reason for the failure to delete the work order resource in the resource list.

[0084] In one example, when all work order resources in the resource list are successfully deleted, the server can publish a cleanup success event. The server can also change the work order status in the work order list to pending restart. This pending restart status indicates that all previously created work order resources in the work order have been deleted, and the server can recreate the work order.

[0085] In another example, when at least one work order resource in the work order list fails to be deleted, the server can publish a cleanup failure event. The server can modify the work order status in the work order list to cleanup failure. During the above-mentioned work order resource deletion process, the server deletes the work order resources of the work order one by one according to the resource list. When a work order resource fails to be deleted, the server will record the result of the deletion failure. Optionally, during a deletion process, when a work order resource fails to be deleted, the server will not retry to delete the work order resource. The server will continue to delete the next work order resource. Optionally, during a deletion process, when a work order resource fails to be deleted, the server can attempt to delete the work order resource multiple times according to a preset number of retries. If the work order resource is successfully deleted within the number of retries, the server will continue to delete other work order resources. If the work order resource is still not successfully deleted when the number of retries is exhausted, the server will abandon the deletion of the work order resource and continue to delete other work order resources. Optionally, the server may generate a deletion failure reminder based on the resource information of the work order resource that failed to be deleted, so as to inform the technician that the deletion of the work order resource failed, and the technician may analyze the deletion failure of the work order resource.

[0086] In one example, each time the server modifies the work order status corresponding to a work order in the work order list, it needs to query and verify the current status of the work order. Specifically, the server can obtain the current status of the work order and compare the current status with the target status that needs to be modified. If the current status is consistent with the target status, it means that the work order is already in the target state. If the current status is inconsistent with the target status, it means that the work order status needs to be modified. Optionally, the server can also verify whether the jump from the current state to the target state of the work order is correct. Specifically, in this step, the target state can be to be cleared. In this embodiment, in order to reduce repetition and redundancy, the server no longer adds the query and verification process each time the work order status is modified, but in actual processing, the server will perform the query and verification process in this example each time the work order status is modified.

[0087] S103. When the resource quantity is 0, the work order status of the work order list is changed to pending retry, and the work order resources of the work order are recreated.

[0088] In this embodiment, the server can determine whether the resource quantity is 0. Optionally, the server can determine whether the resource quantity is 0 after step S101. Optionally, the server can also determine whether the resource quantity is 0 after completing the execution of step S102 and re-acquiring the resource quantity. When the resource quantity is 0, it means that the work order resource of the work order has not been successfully created. At this time, the server can modify the work order status in the work order list to be retried. The work order status to be retried is used to indicate that the server can recreate the instance of the work order. Specifically, the server can achieve the re-creation of the work order by recreating the work order resource of the work order.

[0089] Optionally, since the resource quantity is the number of work order resources with a successful status corresponding to the work order in the resource list, when the resource quantity for the work order resource is 0, there may be work order resources that failed to be deleted. Therefore, before changing the work order status to pending retry, the server may obtain the number of work order resources with a failed status corresponding to the work order in the resource list. If this number is 0, the server will change the work order status of the work order in the work order list to pending retry. Otherwise, if this number is greater than or equal to 0, the server may obtain the resource number of the work order resource with a failed status. The server may generate a failure notification based on the work order number. Optionally, the server may also obtain the failure reason for the work order resource with a failed status from the resource list. The server may generate a failure notification based on the failure reason. Based on the failure notification, the technician can repair the work order resource to allow it to be deleted normally. Optionally, after repairing all work order resources in the failure notification, the technician can click the Clean button to clean up the work order resources for the work order again.

[0090] The work order exception handling method provided in the present application is that the server can create work order resources one by one according to the work order after obtaining the work order. When a work order resource is created abnormally, the server can publish an exception handling event. The server can query the work order resources that have been successfully created for the work order in the resource list based on the work order number, and count the number of resources of the work order resources. When the number of resources is greater than or equal to 1, the server can modify the work order status in the work order list to be cleared. The server can also delete the work order resources based on the resource list. When the number of resources is 0, the server can modify the work order status in the work order list to be retried. The server can also recreate the work order resources of the work order. In the present application, by modifying the work order status in the list when the work order resource is created abnormally, the work order status is displayed, so that the technical staff can determine the creation status of the work order based on the work order status. In the present application, by deleting the work order resources that have been created by the work order, the deletion and release of resources in the work order instance are realized, thereby improving resource utilization.

[0091] Based on the above embodiment, when the server determines that the number of work order resources created by the work order is greater than or equal to 0, the server can delete these work order resources. Figure 3 As shown, taking the Server Load Balancer (SLB) service as an example, it is assumed that the SLB work order specifically includes four steps: creating the SLB itself, creating IPv4 bandwidth, creating an IPv4 elastic public IP (Elastic IP, EIP), and binding the IPv4 EIP to the SLB. This example assumes that the SLB work order fails at the step of binding the EIP to the SLB. In the above embodiment, the process of deleting the work order resources of the SLB work order can specifically include the following steps:

[0092] S201. When the technician checks the SLB work order list and finds that the work order status is to be cleared, he clicks the Clear button.

[0093] S202. The server saves the work order number of the SLB work order into a thread variable (ThreadLocal).

[0094] S203. The server may query the resource list for the work order resources and resource quantity that have been successfully created for the SLB work order according to the work order number.

[0095] S204: The server determines whether the resources for the work order are empty by checking whether the resource count of the successfully created work order resource is 0. If the resource count is 0, the resources for the work order are empty, and the server executes step S220. Otherwise, if the resource count is not 0, the resources for the work order are not empty, and the server executes step S205. Assume that if the resource count is not 0, the SLB work order may include three successfully created work order resources.

[0096] S205: If the work order's resources are not empty, clean up the resources, adhering to the principle of cleaning up newly created resources first. Therefore, after this step, the server can proceed to S210 and begin cleaning up the work order resources. Simultaneously, the server also needs to proceed to S206 and subsequent steps to complete the event publishing and work order status modification during this operation.

[0097] S206: When the server starts to clean up the work order resources, the server may publish a start cleanup event.

[0098] S207. The server may call the work order state machine processor and obtain the work order number through ThreadLocal.

[0099] S208. The server may query the work order status of the work order corresponding to the work order number through the resource processing state machine. The server may also verify the work order status. If the verification is successful, the server may proceed to step S209. Otherwise, the server may terminate the operation corresponding to the work order.

[0100] S209. The server changes the work order status to being cleaned up.

[0101] S210: The server determines whether there are any work order resources that need to be cleared based on the number of work order resources that have been created. If there are any work order resources that need to be cleared, the server proceeds to step S211. Otherwise, the server jumps to step S214.

[0102] In this step, as the work order resources that have already been created are deleted during the subsequent cleanup process, the resource quantity will also be modified. It should be noted that the work order resources that need to be cleaned in this step are those that have not been cleaned up. After a work order resource is cleaned up in step S211, regardless of whether the cleanup operation is successful, it will not be counted as a work order resource that needs to be cleaned up.

[0103] For example, the server first retrieves a resource quantity of 3 work order resources. After the server completes the cleanup of work order resources 1 and 2, some work order resources still need to be cleaned up. When the server continues to clean up work order resource 3, all work order resources are cleaned up. If the cleanup of work order resource 3 fails, all work order resources are still considered cleaned up.

[0104] S211: The server performs resource cleanup operations.

[0105] In this step, the server may clear work order resources one by one. Optionally, while clearing each work order resource, the server may continue to execute S212 and subsequent steps to complete the event publishing and work order status modification during this operation. Optionally, after completing the clearing of a work order resource, the server may jump to step S210 to perform a determination. Optionally, a time threshold may be preset in the server during the clearing of work order resources. If the server's loop duration for executing steps S210 and S211 exceeds this time threshold, the deletion of the work order resource may enter an infinite loop. Therefore, the server may terminate the clearing of the work order resource and report an error. Optionally, after completing the clearing of all work order resources, the server may jump to step S210 to perform a determination. Optionally, a number threshold may be preset in the server during the clearing of work order resources. If the server's loop duration for executing steps S210 and S211 exceeds this number threshold during the deletion of a work order resource, the deletion of the work order resource may enter an infinite loop. Therefore, the server can end the cleanup of the work order resource and report an error.

[0106] S212: When the server starts to clean up the work order resources, the server may publish a resource cleanup event.

[0107] In this step, the server publishes a resource cleanup event for each work order resource cleanup. For example, if an SLB work order includes three successfully created work order resources, the server will publish a total of three resource cleanup events.

[0108] S213. The server may call the work order state machine processor to logically delete the vm_create_resource_record record corresponding to the resource number.

[0109] In this step, the resource information of each work order resource may include a resource ID. The resource ID may be stored in the resource list. The server may delete the vm_create_resource_record record corresponding to each work order resource based on the resource ID.

[0110] Optionally, after completing the deletion in this step, the server may also modify the status of the work order resource of the work order in the resource list to deletion according to the work order state machine processor.

[0111] S214: The server may analyze the cleanup result of step S211 to determine whether all the work order resources created for the work order have been successfully cleaned up. If all have been successfully cleaned up, the server may jump to step S220. Otherwise, the server may execute step S215.

[0112] S215: If there is a resource cleanup failure during the resource cleanup process, the server may throw an exception. While throwing the exception, the server may continue to execute S216 and subsequent steps to complete the release of the event and the modification of the work order status during the operation.

[0113] S216. When the server throws an exception, the server may publish a cleanup failure event.

[0114] S217. The server can call the work order state machine processor and obtain the work order number through ThreadLocal.

[0115] S218. The server may query the work order status of the work order corresponding to the work order number through the resource processing state machine. The server may also verify the work order status. If the verification is successful, the server may continue to execute step S209. Otherwise, the server may terminate the operation corresponding to the work order.

[0116] S219. The server changes the work order status to cleanup failure.

[0117] S220, the server completes the clearing of the work order resource of the work order. Meanwhile, the server can continue to execute S221 and the steps thereafter, complete the publishing of events and the modification of the work order status in the operation process.

[0118] S221, the server can publish a clearing success event.

[0119] S222, the server can call the work order status machine processor to obtain the work order number through ThreadLocal.

[0120] S223, the server can query the work order status of the work order corresponding to the work order number through the resource processing status machine. The server can also verify the work order status. When the verification is successful, the server can continue to execute step S209. Otherwise, the server can end the operation corresponding to the work order.

[0121] S224, the server modifies the work order status of the work order to clearing success.

[0122] Figure 4 A flowchart of a work order exception processing method provided by an embodiment of the application is shown. In the embodiment, the method can include the following steps: Figures 1 to 3 Based on the embodiment shown, as shown in the embodiment, the method provided by the embodiment can include the following steps: Figure 3 As the execution subject of the server, the method of the embodiment can include the following steps:

[0123] S301, obtain a work order, publish a start processing event, save the work order information of the work order to a work order list, and modify the work order status of the work order list to in execution. Wherein, the work order information at least includes a work order number.

[0124] In the embodiment, the server can obtain a work order. The work order can be created by a user through a user terminal. Alternatively, the work order can also be created through a clerk terminal, a business hall terminal or other devices. The server can publish a start processing event of the work order after obtaining the work order. The start processing event is used to indicate that the work order starts to be created. The server can add the work order information of the work order to a work order list. The server can modify the work order status of the work order in the work order list to in execution. Wherein, the work order information of the work order at least includes a work order number of the work order.

[0125] S302, according to the work order, create a work order resource one by one, and when each work order resource is successfully created, publish a resource creation event, and store the work order information of the work order and the resource information of the resource to a resource list. Wherein, the resource information at least includes a resource number.

[0126] In this embodiment, the server can create the required work order resources in the work order one by one based on the work order. Optionally, the server can create an instance for each work order resource. When a work order resource is successfully created, the server can publish a creation success event of the work order resource. The creation success event is used to indicate that the work order resource in the work order is successfully created. The server can save the resource information of the successfully created work order resource in a resource list. In order to facilitate the distinction between work order resources of different work orders, the resource list can also include work order information. Optionally, the work order information in the resource list includes at least the work order number of the work order. Among them, the resource information includes at least the resource number of the work order resource. Optionally, the resource number can be set according to the resource type, and the same resource can correspond to the same resource number. The server can uniquely determine a work order resource based on the combination of the work order number and the resource number. Optionally, the resource number can uniquely correspond to a work order resource.

[0127] In one example, the process of the server creating work order resources for each work order may specifically include:

[0128] Step 1: The server determines the creation method of the work order resource based on the code arrangement of each work order resource. The creation methods include synchronous creation and asynchronous creation.

[0129] Step 2: The server calls the interface corresponding to the work order resource according to the creation method of the work order resource to create the work order resource.

[0130] Step 3: The server obtains the creation result of each work order resource, including creation success and creation failure.

[0131] In this step, the server can determine whether the work order resource was successfully created based on the data returned by the interface. Optionally, the server can also set a time threshold. If the interface corresponding to the work order resource still does not return information after the time threshold has expired, the server can determine that the creation result of the work order resource is a creation failure.

[0132] S303. When all the work order resources of the work order are created successfully, a processing success event is published, and the work order status of the work order list is changed to success.

[0133] In this embodiment, the server can create work order resources sequentially. The server can publish a successful processing event when the last work order resource is created. Optionally, because the interface corresponding to the work order resource is asynchronous, the event of the work order resource creation completion may be unrelated to the order of the work order resources in the work order. Therefore, the server can set a statistical variable for each work order. The server can add 1 to the statistical variable when a work order resource for the work order is created. The server can use this statistical variable to determine whether all work order resources for the work order have been created.

[0134] S304, when the resource creation of the work order is abnormal, a processing exception event is published, and the work order resource that has been successfully created by the work order and the resource quantity of the work order resource are obtained from the resource list.

[0135] S305, when the resource quantity is greater than or equal to 1, the state of the work order in the work order list is modified to be pending cleaning, and the work order resource is deleted according to the resource list.

[0136] S306, when the resource quantity is 0, the state of the work order in the work order list is modified to be pending retry, and the resource of the work order is re-created.

[0137] The steps S304 to S306 are similar to the implementation of the steps S101 to S103 in the embodiment, and will not be described here. Figure 2 The steps S101 to S103 in the embodiment are implemented in a similar manner, and will not be described here.

[0138] The work order exception processing method provided in the application, the server can publish a start processing event after obtaining the work order. The server can save the work order information of the work order to the work order list, and modify the state of the work order list to be in execution. The work order information at least includes a work order number. The server can create the work order resource of the work order one by one, and publish a resource creation event when each work order resource is successfully created. The server can store the work order information of the work order that is successfully created and the resource information of the resource to the resource list. The resource information at least includes a resource number. When all the work order resources of the work order are successfully created, the server can publish a processing success event. The server can modify the state of the work order list to be successful. When the resource creation of the work order is abnormal, the server can publish a processing exception event. The server can obtain the work order resource that has been successfully created by the work order and the resource quantity of the work order resource from the resource list. When the resource quantity is greater than or equal to 1, the server can modify the state of the work order in the work order list to be pending cleaning, and delete the work order resource according to the resource list. When the resource quantity is 0, the server can modify the state of the work order in the work order list to be pending retry, and re-create the resource of the work order. In the application, the deletion and release of the work order resource are realized by deleting the work order resource that has been successfully created by the work order, and the resource utilization rate is improved.

[0139] On the basis of the above-mentioned embodiments, taking the SLB work order of Figure 3 as an example, as shown in Figure 5 , the execution process of the SLB work order can include:

[0140] S401, the server obtains the SLB work order request sent by other terminals.

[0141] S402: The server starts processing the work order. After the server starts processing the work order, it can execute S406 and subsequent steps to complete operations such as modifying the work order status.

[0142] S403: The server may publish a start processing event.

[0143] S404. The server may save the work order information to ThreadLocal through the work order state machine processor.

[0144] S405: The server may modify the work order status of the work order in the work order list to being executed.

[0145] S406. The server can obtain work order information through ThreadLocal

[0146] S407. The server may insert a vm_operate_resource_params record.

[0147] In this step, the server can insert the work order information obtained in step S406 as a record into the work order list. Specifically, the work order information can be a row in the work order list. In this example, the table name of the work order list can be vm_operate_resource_params. Optionally, the work order list can be displayed on a display page. The technician can use the display page to determine the status of the SLB work order and thus determine whether a retry or cleanup is required. Specifically, the server can save the work order information and the work order processing method information in the vm_operate_resource_params. The work order processing method information is used to implement a reflective call during the retry process of step S435.

[0148] S408: The server may determine whether a work order resource needs to be created. If so, the server may proceed to step S409. Otherwise, the server may proceed to step S422 to determine whether an exception occurs during the synchronization process of resource creation.

[0149] S409: The server may determine whether the work order resource was created synchronously or asynchronously. If the work order resource was created synchronously, the server may proceed to step S410. Otherwise, if the work order resource was created asynchronously, the server may proceed to step S415.

[0150] In this step, when there is a work order resource that needs to be created, the server can sequentially obtain a work order resource that needs to be created based on the work order. The server can determine whether the resource creation method of the work order resource is synchronous creation or asynchronous creation based on the code arrangement.

[0151] S410: The server creates the work order resource.

[0152] S411: The work order resource is created successfully. Meanwhile, the server may execute step S412 and subsequent steps after the work order resource is created successfully to complete operations such as modifying the work order status. Optionally, the successful creation of the work order resource includes the successful synchronous creation of step S410 and the successful asynchronous creation of steps S415 to S419.

[0153] S412: The server issues a resource creation event. The resource creation event may include resource information of the currently created work order resource. The resource information may include at least a resource ID.

[0154] S413. The server can obtain the work order information through the resource processing event processor through ThreadLocal.

[0155] S414. The server may write a record in vm_create_resource_record.

[0156] In this step, the server may insert the work order information obtained in step S413 as a record into the resource list. Specifically, the work order information may include the work order number. The server may also determine the currently processed work order resource based on the work order information and write the work order resource into the resource list. Specifically, the resource list may include the work order number, resource number, and resource destruction method information. The resource destruction method information is used to destroy the successfully created work order resource if the work order creation fails.

[0157] S415. The server saves the work order information to Redis. Optionally, the server can save the resource information of the currently processed work order resource to Redis.

[0158] S416. The server's message queue (MQ) may send a resource creation request. Optionally, the server may send the resource creation request to Yunchang. Optionally, Yunchang may be a platform for asynchronously creating the work order resource.

[0159] S417: The server receives the MQ message. Optionally, the MQ message may be information related to the creation result of the work order resource fed back by Yunchang.

[0160] S418. The server obtains the work order information from Redis so that the server can switch to the process corresponding to the work order and continue execution.

[0161] S419. The server saves the work order information to ThreadLocal.

[0162] S420: The server determines whether the work order resource is created successfully. If so, the server jumps to step S411. Otherwise, the server executes step S421.

[0163] S421. The server may throw an exception when the creation is unsuccessful. If the server throws an exception, it is OK to jump to step S423.

[0164] S422: After no more work order resources need to be created, the server may determine whether an exception occurred during the synchronous execution. If an exception occurred, the server proceeds to step S423. Since the asynchronous exception has already been thrown, if no exception occurred, it indicates that all work order resources for the work order have been successfully created, and the server proceeds to step S429.

[0165] S423: The server publishes a handling exception event. For example, in this example, the server might encounter an exception while creating an IPv4 EIP while processing an SLB work order. In this case, the server publishes a handling exception event.

[0166] S424. The server can obtain the work order information through the work order status processor through ThreadLocal.

[0167] S425: The server may query the current state of the resource processing state machine.

[0168] S426. The server determines whether a work order resource has been created. Specifically, the server determines whether a work order resource has been successfully created for the work order. If so, the process proceeds to step S427. Otherwise, if no work order resource has been successfully created, the process proceeds to step S428.

[0169] S427. If there is a work order resource that has been successfully created, the server changes the work order status of the work order in the work order list to pending cleanup.

[0170] In this step, for example, before creating an IPv4 EIP, the server has already completed the SLB creation and IPv4 bandwidth creation steps. Therefore, the server can change the status to pending cleanup. It is important to note that if the failed EIP instance creation has returned the EIP's Universally Unique Identifier (UUID), this indicates that the EIP instance's resources were successfully created, but the creation ultimately failed due to other reasons such as a network outage. In this case, since the server has already returned the EIP's UUID, it is necessary to publish a resource creation event before issuing a work order to handle the exception event to ensure that the EIP resources can be deleted during the resource deletion process.

[0171] S428. If there is a work order resource that has been successfully created, the server changes the work order status of the work order in the work order list to pending retry.

[0172] S429. The entire resource creation process is executed successfully.

[0173] S430: The server may publish a successful processing event.

[0174] S431. The server can obtain the work order information through the work order status processor through ThreadLocal.

[0175] S432: The server may query the current state of the resource processing state machine.

[0176] S433. The server changes the work order status of the work order in the work order list to success.

[0177] S434. When the work order status of the SLB work order in the work order list is pending retry, the server can obtain a retry instruction triggered by the technician clicking the retry button.

[0178] S435. The server may query information on the method for processing the SLB work order.

[0179] In this step, the method for processing the SLB work order may include information such as the work order resources that the SLB work order needs to process, the deletion or release method of each work order resource, etc. Optionally, the processing method information of the SLB work order can be stored in the work order list. Optionally, the processing method for each work order resource of the SLB work order can be stored in the resource list. Therefore, the server can obtain the processing method by querying the work order list and / or resource list. After the server completes the query for the processing method of the SLB work order, the server can jump to step S402 to implement the reflective call.

[0180] Figure 6 A schematic diagram of the structure of a work order exception processing device provided by an embodiment of the present application is shown. Figure 6 As shown, the work order exception handling device 10 of this embodiment is used to implement the operation corresponding to the server in any of the above method embodiments. The work order exception handling device 10 of this embodiment includes:

[0181] The acquisition module 11 is used to publish a processing exception event when a resource creation exception occurs in a work order, and obtain the work order resources that have been successfully created and the resource quantity of the work order resources from the resource list;

[0182] The processing module 12 is configured to modify the state of the work order in the work order list to be cleaned up when the number of resources is greater than or equal to 1, and delete the resource of the work order according to the resource list; and modify the state of the work order in the work order list to be retried when the number of resources is 0, and re-create the resource of the work order.

[0183] Optionally, the processing module 12 is specifically configured to:

[0184] publish a start cleaning event, and modify the state of the work order in the work order list to be cleaned up;

[0185] for each work order resource, publish a resource cleaning event, and delete the record corresponding to the resource number of the work order resource.

[0186] Optionally, the processing module 12 is further configured to:

[0187] when all the work order resources in the resource list are successfully deleted, publish a cleaning success event, and modify the state of the work order in the work order list to be restarted.

[0188] when there is a work order resource in the resource list that fails to be deleted, publish a cleaning failure event, and modify the state of the work order in the work order list to cleaning failure.

[0189] Optionally, the processing module 12 is further configured to:

[0190] obtain a work order, publish a start processing event, save the work order information of the work order to the work order list, and modify the state of the work order in the work order list to be executed;

[0191] create the work order resource of the work order one by one according to the work order, and when each work order resource is successfully created, publish a create resource event, and store the work order information of the work order and the resource information of the resource to the resource list;

[0192] wherein the work order information at least includes a work order number, and the resource information at least includes a resource number.

[0193] Optionally, the processing module 12 is specifically configured to:

[0194] determine the creation mode of the work order resource according to the code arrangement of each work order resource, the creation mode including synchronous creation and asynchronous creation;

[0195] according to the creation mode of the work order resource, call the interface corresponding to the work order resource to create the work order resource.

[0196] Optionally, the processing module 12 is further configured to:

[0197] when all the work order resources of the work order are successfully created, publish a processing success event, and modify the state of the work order in the work order list to success.

[0198] Optionally, before modifying the work order status of the work order list, the method further comprises:

[0199] querying and verifying the current status of the work order.

[0200] The work order exception processing apparatus 10 provided by the embodiments of the present application can execute the method embodiments, and the specific implementation principles and technical effects can be referred to the method embodiments, which will not be described here again.

[0201] Figure 7 A hardware structure schematic diagram of a server provided by the embodiments of the present application is shown. As shown in the figure, Figure 7 The server 20 is used to implement the operations corresponding to the server in any of the method embodiments. The server 20 of the embodiments can include a memory 21, a processor 22 and a communication interface 24.

[0202] The memory 21 is used to store computer execution instructions. The memory 21 can include a high-speed random access memory (RAM), and can also include a non-volatile memory (NVM), for example, at least one disk memory, and can also be a U disk, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0203] The processor 22 is used to execute the computer execution instructions stored in the memory to implement the work order exception processing method in the above embodiments. Details can be referred to the related description in the method embodiments. The processor 22 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC) and the like. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the disclosed method can be directly embodied as hardware processor execution, or executed by a combination of hardware and software modules in the processor.

[0204] Optionally, the memory 21 can be independent or integrated with the processor 22.

[0205] When the memory 21 is a device independent of the processor 22, the server 20 may further include a bus 23. The bus 23 is used to connect the memory 21 and the processor 22. The bus 23 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be divided into address buses, data buses, control buses, etc. For ease of presentation, the buses in the drawings of this application are not limited to only one bus or one type of bus.

[0206] The communication interface 24 may be connected to the processor 21 via the bus 23. The processor 22 may control the communication interface 24 to implement communication with other terminals.

[0207] The server provided in this embodiment can be used to execute the above-mentioned work order exception handling method. Its implementation method and technical effects are similar and will not be repeated here in this embodiment.

[0208] The present application also provides a computer-readable storage medium, in which a computer execution program is stored. When the computer execution program is executed by a processor, it is used to implement the methods provided in the various embodiments described above.

[0209] Among them, the computer-readable storage medium can be a computer storage medium or a communication medium. The communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The computer storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, a computer-readable storage medium is coupled to a processor so that the processor can read information from the computer-readable storage medium and write information to the computer-readable storage medium. Of course, the computer-readable storage medium can also be an integral part of the processor. The processor and the computer-readable storage medium can be located in an application-specific integrated circuit (ASIC). In addition, the ASIC can be located in a user device. Of course, the processor and the computer-readable storage medium can also exist in a communication device as discrete components.

[0210] Specifically, the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random-access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0211] The present application also provides a computer program product, comprising a computer executable program stored in a computer-readable storage medium. At least one processor of a device can read the computer executable program from the computer-readable storage medium, and at least one processor executes the computer executable program so that the device implements the methods provided in the various embodiments described above.

[0212] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0213] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0214] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0215] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0216] If the integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0217] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0218] In the above embodiments, the description of each embodiment has its own focus. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0219] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0220] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for handling work order exceptions, characterized in that: The method comprises: When a resource creation exception occurs for a work order, an exception handling event is published, and the work order resources for which the work order has been successfully created and the resource quantity of the work order resources are obtained from the resource list; When the number of resources is greater than or equal to 1, the work order status corresponding to the work order in the work order list is changed to pending cleanup, and the work order resources are deleted according to the resource list; When the resource quantity is 0, the work order status of the work order list is modified to pending retry, and the work order resource of the work order is recreated.

2. The method according to claim 1, characterized in that Deleting the work order resource according to the resource list specifically includes: Publish a start cleanup event and modify the work order status in the work order list to be cleaned up; For each of the work order resources, a resource cleanup event is issued, and the record corresponding to the resource number of the work order resource is deleted.

3. The method according to claim 2, characterized in that The method further comprises: When all the work order resources of the work order in the resource list are deleted successfully, a cleanup success event is issued, and the work order status in the work order list is changed to pending restart; When the work order resource of the work order in the resource list fails to be deleted, a cleanup failure event is issued, and the work order status in the work order list is modified to cleanup failure.

4. The method according to any one of claims 1 to 3, characterized in that Before obtaining the resource for which the work order has been successfully created from the resource list, the method further includes: Obtain a work order, publish a start processing event, save the work order information of the work order to a work order list, and change the work order status in the work order list to being executed; According to the work order, create the work order resources of the work order one by one, and when each work order resource is successfully created, publish a resource creation event, and store the work order information of the work order and the resource information of the resource in a resource list; The work order information at least includes the work order number, and the resource information at least includes the resource number.

5. The method according to claim 4, characterized in that The step of creating work order resources for the work orders one by one according to the work orders specifically includes: Determining a creation method of the work order resource according to the code arrangement of each work order resource, wherein the creation method includes synchronous creation and asynchronous creation; According to the creation method of the work order resource, calling the interface corresponding to the work order resource to create the work order resource; The creation result of each work order resource is obtained, wherein the creation result includes creation success and creation failure.

6. The method according to claim 5, characterized in that The method further comprises: When all the work order resources of the work order are created successfully, a processing success event is issued, and the work order status of the work order list is modified to success.

7. The method according to any one of claims 1 to 3, characterized in that Before modifying the work order status of the work order list, the method further includes: Query and verify the current status of the work order.

8. A work order exception processing device, characterized in that: include: The acquisition module is used to publish a processing exception event when a resource creation exception occurs in a work order, and obtain the work order resources for which the work order has been successfully created and the resource quantity of the work order resources from the resource list; A processing module is used to modify the work order status in the work order list to be cleared when the number of resources is greater than or equal to 1, and delete the work order resources according to the resource list; when the number of resources is 0, modify the work order status in the work order list to be retried, and recreate the resources of the work order.

9. A server, characterized in that: include: a processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images