CN108519920B

CN108519920B - Scheduling retry method and device

Info

Publication number: CN108519920B
Application number: CN201810211538.5A
Authority: CN
Inventors: 何青松; 周仕成; 王新盟; 李联邦
Original assignee: Koubei Shanghai Information Technology Co Ltd
Current assignee: Koubei Shanghai Information Technology Co Ltd
Priority date: 2018-03-14
Filing date: 2018-03-14
Publication date: 2020-12-01
Anticipated expiration: 2038-03-14
Also published as: CN108519920A

Abstract

The application provides a scheduling retry method, which comprises the following steps: determining the job scheduling processing exception type according to the specific exception condition when the job scheduling processing exception is processed: determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up. Therefore, according to the technical scheme, different scheduling strategies are adopted for scheduling and processing the exception according to different jobs, the exception processing efficiency is improved, and system resources during scheduling retry are saved.

Description

Scheduling retry method and device

Technical Field

The application relates to the field of computer scheduling methods, in particular to a scheduling retry method and a scheduling retry device. The application also relates to an electronic device for scheduling retries and a computer-readable storage medium.

Background

In a large network architecture, a service action request often needs to be completed through multiple system calls, including relatively time-consuming operations such as intersystem call, data calculation, data storage, and the like. If the conditions of intersystem call exception, service data exception, interface call timeout and the like are met, the initiating system needs to perform scheduling retry so as to continue to advance and execute the service action request. The scheduling retry strategy directly determines how long the service action can be advanced to success, how much resource the scheduling retry consumes, and other practical problems. Therefore, the selection of the scheduling retry strategy is germane to the successful execution of the push execution service action request.

In the prior art, a scheduling retry strategy adopts an equal-difference time interval mode to cope with all abnormal scenes. The method has obvious defects that the interval time of the equal-difference intervals cannot be reasonably determined, system resources are wasted if the time interval is too small, the time cost for advancing to success is increased if the time interval is large, and scheduling retry is not necessary for some exceptions which cannot be successfully scheduled and retried. For example, scheduling for some exception scenarios can never be advanced to success, requiring manual intervention to resolve, and scheduling retries for such exceptions are unnecessary. For another example, some abnormal scenarios cannot be advanced to success in a short time, so scheduling retries in a short time wastes time and system resources. In addition, some exceptions can be successfully scheduled for retry in a short time, and under the equal-difference time interval strategy, the next scheduled retry can be performed after a longer time interval, which is low in efficiency.

Disclosure of Invention

The application provides a scheduling retry method, which aims to solve the problems that the existing scheduling retry method is low in abnormal processing efficiency and wastes system resources during scheduling retry.

The application provides a scheduling retry method, which comprises the following steps: determining the type of the job scheduling processing exception according to the specific exception condition when the job scheduling processing exception; determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up.

Optionally, before determining the job scheduling processing exception type according to the specific exception condition when the job scheduling processing exception is performed, the method further includes: after receiving an action request of an action initiator, requesting a server to verify the information of the action initiator; after receiving the information that the information of the action initiator sent by the server passes the verification, confirming the current action request to the action initiator to be successfully executed; and according to the action request, carrying out job scheduling of the job required by the action request.

Optionally, the job scheduling processing exception type at least includes one of the following: exceptions that cannot be resolved by scheduling retries, dependent job handling exceptions, sporadic handling exceptions, system exceptions, or call timeout exceptions.

Optionally, if the job scheduling processing exception type is the exception which cannot be solved through scheduling retry, determining whether to perform next scheduling retry according to the determined job scheduling processing exception type, and determining whether to perform the next scheduling retry; and further performing the steps of: and executing alarm operation.

Optionally, if the job scheduling processing exception type is a system exception or a call timeout exception, determining whether a next scheduling retry is required according to the determined job scheduling processing exception type, and determining that the result is yes; the scheduling strategy is a Fibonacci gradient sequence strategy, namely, the time interval of the next scheduling retry is determined according to the Fibonacci gradient sequence.

Optionally, if the job scheduling processing exception type is an occasional processing exception, determining whether a next scheduling retry is required according to the determined job scheduling processing exception type as a yes judgment result; the scheduling strategy short time interval strategy is that the time interval of the next scheduling retry is a short time interval.

Optionally, if the job scheduling processing exception type is a job-dependent processing exception, determining whether a next scheduling retry is required according to the determined job scheduling processing exception type as a yes judgment result; the scheduling strategy is a long time interval strategy, namely the time interval of the next scheduling retry is a long time interval.

Optionally, after the performing the alarm operation, the method further includes: when the abnormity which cannot be solved through the scheduling retry is determined to be caused by account logout, acquiring credit information of a user corresponding to the account, wherein the credit information comprises credit level and credit score; and adjusting the credit score and the credit level of the user according to a preset credit management rule.

Optionally, the determining, by using the scheduling policy, a time of a next scheduling retry, and executing the next scheduling retry when the time arrives specifically includes: determining the time of the next scheduling retry by adopting the Fibonacci delivery strategy; determining whether the time of the next scheduling retry determined according to the Fibonacci gradient sequence exceeds a preset time interval threshold; if not, the next scheduling retry is executed when the time arrives.

Optionally, the determining, by using the scheduling policy, a time of a next scheduling retry, and executing the next scheduling retry when the time arrives specifically includes: determining the time of next scheduling retry by adopting the short time interval strategy; counting the execution times of the time step for determining the next scheduling retry by adopting the short time interval strategy; and when the execution times do not exceed the preset time threshold, executing the next scheduling retry.

Optionally, before the determining the time of the next scheduling retry by using the scheduling policy, the method further includes: when determining that the dependent job processing exception type is caused by account freezing, acquiring account freezing information, wherein the account freezing information comprises an account freezing period; determining whether the freezing time limit is smaller than a preset freezing time limit threshold value; if yes, executing the next step.

Optionally, after determining whether the freezing duration is smaller than a preset freezing duration threshold, before the step of executing the next step, the method further includes: when the account freezing period is over, detecting whether the account freezing is removed; if yes, executing the next step.

Optionally, before determining the time of the next scheduling retry by using the scheduling policy, the method further includes: when determining that the operation-dependent processing exception type is caused by account fund shortage, acquiring associated account information of the account with insufficient fund; and taking the associated account as an object of next scheduling retry.

Optionally, the job scheduling processing exception is generated at the following stage: a local data processing phase or/and a remote system processing phase is invoked.

Optionally, the type of the sporadic processing exception includes a processing exception caused by network jitter.

The present application also provides a scheduling retry apparatus, comprising: the abnormal type determining unit is configured for determining the abnormal type of the job scheduling processing according to the specific abnormal condition when the job scheduling processing is abnormal; the scheduling strategy obtaining unit is configured to determine whether to perform next scheduling retry according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and the scheduling retry unit is configured to determine the time of the next scheduling retry by adopting the scheduling strategy if the next scheduling retry is required, and execute the next scheduling retry when the time is up.

Optionally, the apparatus further comprises: the verification request unit is configured to request the server to verify the information of the action initiator after receiving the action request of the action initiator; the confirmation unit is configured to confirm that the current action request is successfully executed to the action initiator after receiving the information that the information of the action initiator sent by the server passes the verification; and the scheduling unit is configured to perform job scheduling of the job required by the action request according to the action request.

Optionally, the apparatus further comprises: an execution unit, configured to, if the job scheduling processing exception type is the exception that cannot be resolved by the scheduling retry, determine whether a next scheduling retry is required in the step of determining whether the job scheduling processing exception type is the determined job scheduling processing exception type, and after a determination result is no, execute the following steps: and executing alarm operation.

Optionally, the scheduling policy obtaining unit is further configured to determine, if the job scheduling processing exception type is a system exception or a call timeout exception, whether to perform a next scheduling retry according to the determined job scheduling processing exception type, if so; the scheduling strategy is a Fibonacci gradient sequence strategy, namely, the time interval of the next scheduling retry is determined according to the Fibonacci gradient sequence.

Optionally, the scheduling policy obtaining unit is further configured to determine, if the job scheduling processing exception type is an occasional processing exception, whether a next scheduling retry is required to be performed according to the determined job scheduling processing exception type, if so; the scheduling strategy short time interval strategy is that the time interval of the next scheduling retry is a short time interval.

Optionally, the scheduling policy obtaining unit is further configured to determine, if the job scheduling processing exception type is a dependent job processing exception, whether a next scheduling retry is required to be performed according to the determined job scheduling processing exception type, and determine that a result of the determination is yes; the scheduling strategy is a long time interval strategy, namely the time interval of the next scheduling retry is a long time interval.

Optionally, the apparatus further comprises: the credit information acquisition unit is configured to acquire credit information of a user corresponding to an account when the abnormity which cannot be solved through the scheduling retry is determined to be caused by the cancellation of the account, and the credit information comprises credit level and credit score; and the credit information adjusting unit is configured for adjusting the credit score and the credit level of the user according to a preset credit management rule.

Optionally, the scheduling retry unit is specifically configured to: determining the time of the next scheduling retry by adopting the Fibonacci delivery strategy; determining whether the time of the next scheduling retry determined according to the Fibonacci gradient sequence exceeds a preset time interval threshold; if not, the next scheduling retry is executed when the time arrives.

Optionally, the scheduling retry unit is specifically configured to: determining the time of next scheduling retry by adopting the short time interval strategy; counting the execution times of the time step for determining the next scheduling retry by adopting the short time interval strategy; and when the execution times do not exceed the preset time threshold, executing the next scheduling retry.

Optionally, the apparatus further includes an account freezing information obtaining unit configured to obtain account freezing information when it is determined that the dependent job processing exception type is caused by account freezing, where the account freezing information includes an account freezing deadline; the freezing time limit judging unit is configured for determining whether the freezing time limit is smaller than a preset freezing time limit threshold value; if yes, determining to execute the next step.

Optionally, the apparatus further comprises: the detection unit is configured to detect whether account freezing is removed or not when the account freezing period passes; if yes, determining to execute the next step.

Optionally, the device further includes a related account information obtaining unit configured to, when it is determined that the dependence job processing exception type is caused by insufficient funds of the account, obtain related account information of the account with insufficient funds; and the scheduling retry object determining unit is configured to use the associated account number as an object of the next scheduling retry.

The present application also proposes an electronic device for scheduling retries, characterized in that the electronic device comprises: a display; a processor; a memory for storing a program for scheduling retries, which when read executed by the processor performs the following: determining the type of the job scheduling processing exception according to the specific exception condition when the job scheduling processing exception; determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up.

The present application also provides a computer readable storage medium having a retry scheduling program stored thereon, wherein the program when read and executed by a processor performs the following operations: determining the type of the job scheduling processing exception according to the specific exception condition when the job scheduling processing exception; determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up.

According to the technical scheme of the scheduling retry, whether the scheduling retry is necessary or not is determined according to different types of exceptions, and a scheduling retry strategy is obtained when the scheduling retry is determined to be necessary. When the technical scheme determines that the scheduling retry is unnecessary, the scheduling retry is not executed, so that the waste of system resources caused by the unnecessary scheduling retry is avoided. When the technical scheme determines that the scheduling retry is necessary, the scheduling strategy which is suitable for the determined abnormal type is further obtained, the scheduling strategy is adopted to determine the time of the next scheduling retry and the scheduling retry is carried out after the time is reached, so that the corresponding abnormal type is scheduled and retried according to the corresponding strategy, namely the corresponding scheduling retry time is determined instead of uniformly determining the same time interval, which is beneficial to solving the problem of unreasonable time spent in abnormal situations and solving the problem of excessive occupation of system resources during scheduling retry, namely solving the problems of low abnormal efficiency and more occupation of the system resources caused by adopting equal-difference time intervals to determine the next scheduling retry time in the prior art.

In addition, in the preferred technical scheme, for the exception which cannot be solved through the scheduling retry, the scheduling retry is not carried out, and the manual intervention is directly carried out, so that the time spent on the scheduling retry and the occupation of system resources are avoided, and the processing efficiency is improved.

In the preferred technical scheme, for system abnormity or calling overtime abnormity, a Fibonacci gradient sequence is adopted to gradually increase the time interval of next scheduling retry, scheduling retry can be performed according to a short time interval and then according to a long time interval, so that abnormity is tried to be solved quickly firstly, the abnormity is solved after the long time interval when the abnormity cannot be solved quickly, and optimal configuration is realized on the efficiency for processing the abnormity and system resources required by scheduling retry.

In the preferred technical scheme, for the dependence job processing abnormity, the next scheduling retry is carried out after a long time interval is determined, and the waste of system resources caused by scheduling retries in a plurality of short time intervals is avoided.

In the preferred technical scheme, for the sporadic processing of the exception, the next scheduling retry is carried out after a short time interval is determined, so that the efficiency of processing the exception is improved.

In short, the present embodiment can adopt different scheduling strategies for scheduling and processing the exception of different jobs, thereby improving the efficiency of processing the exception and saving system resources during scheduling retry.

Drawings

FIG. 1 is a flow diagram of one embodiment of a method for scheduling retries provided herein;

FIG. 2 is a schematic diagram illustrating an application scenario of the embodiment of the scheduling retry method shown in FIG. 1 of the present application;

fig. 3 is a schematic structural diagram of an embodiment of a scheduling retry apparatus provided in the present application.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.

Fig. 1 is a flowchart of an embodiment of a scheduling retry method provided in the present application, and fig. 2 is a schematic application scenario diagram of the embodiment of the scheduling retry method shown in fig. 1 in the present application. The following describes a technical solution of the scheduling retry method in fig. 1 with reference to the application scenario shown in fig. 2.

Fig. 2 may be understood as a business action scenario for executing a deduction on over a network. In this scenario, the execution of the deduction service action request often requires time-consuming operations such as calling a corresponding processing program, a corresponding processing function, a corresponding computer interface, a corresponding computer system, and the like for many times. If the user is notified of the successful deduction after waiting for such many calls to complete, the user is required to wait for a long time.

In order to inform the user of the result of the successful or unsuccessful deduction in time, in practice, before executing a plurality of scheduling tasks, the scheduling initiating system usually requests the server to verify the information of the action initiating party after receiving the action request of the action initiating party. And as long as the user passes the information verification, the user is directly informed that the deduction request of the user is completed, and then various calls are carried out to complete the actual deduction service so as to be consistent with the previous notice of the client.

The information of the user may be, for example, action request information of the user, credit rating information (e.g., excellent) of the user, credit score information (e.g., 701 scores). The check may be a service check verification, e.g. verifying whether the action request is a payment action request.

The verification may also be data verification, for example, to determine whether the credit rating information and the credit score information of the user meet predetermined requirements, such as a credit rating of above 650 minutes and a credit score of above 650 minutes.

The check may also be a rule check, for example, whether the user's debit action request satisfies a predetermined time rule, such as within a time period from 8 am to 6 pm.

And after receiving the information that the information of the action initiator sent by the server passes the verification, confirming that the current action request is successfully executed to the action initiator. For example, when the action request information of the user is request deduction information, and the credit rating is excellent and the credit score 701 meets the predetermined requirement, a notification that the information verification is passed, which is sent by the server, is received.

The action request initiator may be a real user or a certain system, and the scheduling initiation system refers to a certain computer system.

The above process is called as a synchronous acceptance stage, and in this stage, as long as the information of the user passes through the relevant verification, the user is directly notified that the action request is successfully executed, so that the time is saved, and the efficiency of processing the action request by the user is improved.

After the synchronous accepting stage, the scheduling initiating system starts to execute multiple calls, for example, to call a corresponding processing program, a corresponding processing function, a corresponding computer interface, a corresponding computer system, and other time-consuming operations, that is, to perform job scheduling of the job required by the action request according to the action request.

For example, after receiving the notification of passing the information verification sent by the server, when a part of the amount of money is deducted from the account of the user, the program, the function, and the like needed to be used for executing the series of steps need to be called through the steps of "pushing an order", "obtaining the fund information of the account of the user", "checking whether the amount of money in the account is not less than the amount to be deducted", "calling the user. This process is referred to as the asynchronous processing stage.

When scheduling is performed in the asynchronous processing stage, if conditions such as inter-system call exception, service data exception, interface call timeout and the like are met, the scheduling initiating system needs to perform scheduling retry, wherein the scheduling retry refers to re-executing the call of a program, a function and the like which need to be used, so as to continue to advance and execute the service action request until the service action request is successfully executed. When the service action request is successfully executed, the service action request can be consistent with the action request message which informs the user in advance that the action request message is successfully executed.

In the asynchronous processing stage, when the scheduling initiating system performs scheduling retry, a certain scheduling retry strategy is needed, for example, how long time later the scheduling retry is performed, which directly determines how long the service action can be advanced to success, how much resources of the system are consumed by the scheduling retry, and other practical problems. Therefore, the selection of the scheduling retry strategy is germane to the successful execution of the push execution service action request.

The scheduling retry method shown in fig. 1 is a solution to the core problem of determining the scheduling policy in the asynchronous processing procedure shown in fig. 2, which is explained in detail below. The scheduling retry method is described in detail below with reference to fig. 1.

Step S101, according to the specific abnormal situation when the job scheduling processing is abnormal, determining the abnormal type of the job scheduling processing.

A Job, referred to by the term "Job" in the art of computers, is a general term for performing a series of steps to accomplish one or more tasks. For example, in a scenario that a user purchases on a network platform, when a part of money needs to be deducted from an account of the user, the steps of "obtaining user account information", "checking whether the money in the account is not less than the amount to be deducted", "deducting a certain amount", and the like may be required, and the series of steps may be referred to as an operation.

Job scheduling refers to the performance of one or more tasks, typically requiring that certain step(s) be performed in a certain order. For example, when the previous deduction task is executed, the steps of "obtaining user account information", "checking whether the amount of money in the account is not less than the amount to be deducted", "deducting a certain amount", and the like, need to be sequentially executed in order. When a step is executed, it is possible to make a call to a program, a function, or the like used to execute the step. The scheduling retry refers to re-execution of a call to a program, function, or the like that needs to be used.

The job scheduling processing exception refers to a situation that the whole job process cannot be normally advanced due to the fact that a certain step cannot be successfully executed in the job scheduling processing execution process. The following are common specific exception situations and possible causes of job scheduling processing exceptions: due to account logout, job scheduling processing is abnormal, and due to account logout, a fee cannot be deducted from the account, so that processing is abnormal; the processing is abnormal due to account freezing or account fund shortage, and refund to the account is possibly caused if the account is frozen; the job scheduling processing abnormality caused by the network jitter refers to the job scheduling processing abnormality in a short time due to the fact that a network system is unstable and cannot be connected with an account; a system exception or a call timeout exception, such as an exception of job scheduling processing caused by a long-time failure to successfully call a certain program, function, and the like.

The job scheduling processing exception type is used for classifying various specific job scheduling processing exception conditions. Obviously, the classification can be performed in different ways from different angles according to different purposes; the same specific job scheduling processing exception can belong to several types according to different classification modes. In this embodiment, since the main purpose of classification is to determine a scheduling policy for scheduling retries, classification is performed from the viewpoint of influence on the scheduling policy. Take the above exception of scheduling processing due to account logout as an example. In some scenarios, a logout of an account will result in a failure to deduct money from the account, and even if the deduction request is executed again, the processing exception cannot be successfully executed, and this type of processing exception cannot be resolved by scheduling retry, which may be referred to as an exception type that cannot be resolved by scheduling retry. For another example, the account freezing causes processing abnormality. In some scenarios, since the account may be frozen by the bank account processing system, if a deduction is made to the account, the processing exception may be classified as a dependent job processing exception, which needs to wait for the bank account processing system to unfreeze the account. As another example, the processing exception caused by the network jitter may be referred to as an occasional processing exception type, since the network jitter is generally sporadic, infrequent, and can be quickly reprocessed. For another example, if there is an exception condition of a system exception or a call timeout exception, and it needs to wait for an indefinite time before calling again, the same exception type, that is, the system exception or the call timeout exception, may be included. In many job scheduling systems, an exception code corresponding to a specific exception condition is generated when an exception occurs in job scheduling processing, and the job scheduling processing exception type may be determined according to the specific exception condition when the exception occurs in job scheduling processing. For example, when a specific abnormal condition occurs when a job scheduling processing abnormality occurs (for example, a deduction from an account cannot be made due to account logout), it is detected that the generated preset abnormality code is "00000001", and it is determined that the job scheduling processing abnormality type is an abnormality that cannot be solved by scheduling retry.

In this embodiment, the job scheduling processing exception may be generated at the following stages: a local data processing stage and a remote system calling processing stage. This is because when certain action requests are executed, it is possible that the handling of the exception may occur in both the local system and in other systems in the network. But whether the scheduling processing exceptions occur at data processing stages on the local system or at data processing stages in other remote systems, they may be handled by the solution of the present application.

Step S102, determining whether next scheduling retry is needed or not according to the determined job scheduling processing exception type; and if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type.

The scheduling policy corresponding to the job scheduling processing exception type mainly includes how long it takes to try to execute the target task again, and whether other relevant processing is needed. For example, the deduction task is executed again after 2 seconds.

Determining whether next scheduling retry is needed according to the determined job scheduling processing exception type; and if the determination result is yes, further acquiring a scheduling policy corresponding to the job scheduling processing exception type, "which may specifically be at least one of the following:

if the operation scheduling processing exception type is a system exception or a calling overtime exception, determining whether the judgment result of next scheduling retry is needed to be carried out is yes according to the determined operation scheduling processing exception type; the scheduling strategy is a Fibonacci gradient sequence strategy, namely, the time interval of the next scheduling retry is determined according to the Fibonacci gradient sequence. The fibonacci taper sequence refers to a sequence of numbers 2, 3, 5, 8, 13 characterized by each term being equal to the sum of the first two terms. For example, if a current call times out, such as calling a function, has not been successfully executed for 2 seconds, this type of handling exception is a system exception or call time out exception. In the step of determining whether the next scheduling retry is needed for the system exception or the calling overtime exception, the judgment result is yes; the time interval for the next scheduled retry is further determined to be 3 seconds. If no more execution is successful, it is further determined that the time interval for the next scheduled retry is 5 seconds.

If the job scheduling processing exception type is accidental processing exception, determining whether next scheduling retry is needed or not according to the determined job scheduling processing exception type, wherein the determination result is yes; the scheduling policy is a short interval policy. For example, the handling exception is a sporadic handling exception due to a connection error which happens when the system operation part is stable. In the step of determining whether the next scheduling retry is needed or not for the accidental processing abnormality, the judgment result is yes; the time interval for the next scheduled retry is further determined to be a short time interval, which may be 0.5 seconds, for example.

If the job scheduling processing exception type is dependent on the job processing exception, determining whether the judgment result of next scheduling retry is needed according to the determined job scheduling processing exception type; the scheduling strategy is a long time interval strategy. For example, the reason for the processing exception caused by account freezing is that the account is frozen by the bank account processing system, and in some scenarios, if a deduction is made for the account, the account needs to wait for the bank account processing system to unfreeze, and the processing exception is a job-dependent processing exception type. In the step of determining whether the next scheduling retry is needed or not for the dependent operation processing exception type, the judgment result is yes; it is further determined that the time interval for the next scheduled retry is a longer time interval, such as 2 days elapsed.

If the job scheduling processing exception type is an exception type which cannot be solved through scheduling retry, determining whether the judgment result of next scheduling retry is needed or not according to the determined job scheduling processing exception type; and if the judgment result is negative, further executing the following steps: and executing alarm operation. For example, a processing exception of the type that cannot be resolved by scheduling a retry may not succeed even if a debit request is executed again, due to an account logout that cannot be deducted from the account, or the like. Determining whether the next scheduling retry is needed for the abnormal types which cannot be solved through the scheduling retry, wherein the judgment result is negative; and directly executing an alarm operation step to remind manual intervention and carrying out corresponding manual processing. When the abnormity which can not be solved through the scheduling retry is determined to be caused by account logout, the credit information of the user corresponding to the account can be acquired, and the credit information comprises credit level and credit score. For example, information level information such as "excellent", "good", and the like can be acquired. Credit score information such as "651" score, "701" score, etc. may also be possible. In addition, the credit score and the credit level of the user can be further adjusted according to a preset credit management rule. For example, the preset credit management rule may be: the account is logged off before the debit is made, and the credit score is lowered by one level or adjusted by 50 points. Then, at this step, the credit rating and credit score are adjusted down directly. Therefore, the following technical effects can be achieved: under the abnormal condition, aiming at the abnormity which can not be solved by scheduling retry, the manual intervention is directly reminded, and the efficiency of scheduling retry is improved. Meanwhile, the credit information of the user is adjusted, so that the credit security of the transaction is improved.

After determining that the next scheduling retry is to be performed according to step S102 and obtaining the corresponding scheduling policy, the following step S103 is continued to determine the time of the next scheduling retry by using the scheduling policy, and the next scheduling retry is executed when the time is reached, which will be described in detail below.

And step S103, if the next scheduling retry is needed, determining the time of the next scheduling retry by using the scheduling strategy, and executing the next scheduling retry when the time is up.

After determining the job scheduling processing exception type based on step S102, whether a next scheduling retry is required, and if yes, acquiring a scheduling policy corresponding to the job scheduling processing exception type, determining a time of the next scheduling retry using the scheduling policy, and executing the next scheduling retry when the time arrives.

For example, after determining a system exception or a call timeout exception based on step S102, and determining that a next scheduling retry is required and further acquiring a fibonacci gradient strategy corresponding to the system exception or the call timeout exception, that is, determining a time interval of the next scheduling retry according to the fibonacci gradient sequence, the scheduling strategy is used to determine a time of the next scheduling retry, and the next scheduling retry is executed when the time arrives; after the scheduling retry strategy is adopted, in order to avoid excessive consumption of system resources caused by repeated execution of scheduling retries when the scheduling retries are not successful all the time, a strategy for terminating the scheduling retries may be set in combination with different scheduling retry strategies, for example, in the case of adopting the fibonacci delivery strategy, the following steps are specifically executed: first, the fibonacci delivery strategy is employed to determine the time for the next scheduled retry. For example, if the call is not successfully executed for 2 seconds, the time interval for the next scheduled retry is determined to be 3 seconds, and if the call is not successfully executed any more, the time interval for the next scheduled retry is determined to be 5 seconds. Next, it is determined whether the time for the next scheduled retry, as determined by the fibonacci progression, exceeds a preset time interval threshold. If not, the next scheduling retry is executed when the time arrives. For example, if the determined time interval for the next scheduled retry is less than the preset time interval threshold for 20 seconds for 5 seconds, the next scheduled retry is executed after 5 seconds. If after a number of scheduling retries, it is again determined that the time interval for a scheduling retry exceeds 20 seconds, the next scheduling retry may be terminated.

For another example, when the sporadic processing exception is determined based on step S102, and it is determined that the next scheduling retry is required and a short time interval policy corresponding to the sporadic processing exception is further obtained, that is, the time interval of the next scheduling retry is a short time interval, the scheduling policy is used to determine the time of the next scheduling retry, and the next scheduling retry is executed when the time arrives; in addition, a strategy for terminating and scheduling retry based on the number of retries as termination is also set. The specific execution process comprises the following steps: first, the short time interval strategy is adopted to determine the time of the next scheduling retry. For example, the handling exception is a sporadic handling exception due to a connection error which happens when the system operation part is stable. For such sporadic processing exceptions, the time interval for the next scheduled retry is determined to be a short time interval of 0.5 seconds. Secondly, counting the execution times of the time step for determining the next scheduling retry by adopting the short time interval strategy; and when the execution times do not exceed the preset time threshold, executing the next scheduling retry. For example, after each short time interval for determining the next scheduling retry, the counter (counter) is incremented by 1, and when the number of executions, for example, 5 times, is less than the preset execution threshold value 20 times, the next scheduling retry is executed. Where a counter is a counter that allows a user to create a reference anywhere in a thread group. The counter configuration allows the user to configure the maximum value (e.g. 20 times), and the counter may be set to end after cycling through 20 times.

For another example, when it is determined that the dependent job processing abnormality is caused based on step S102, and it may be further determined whether the dependent job processing abnormality type is caused by freezing of an account number, if it is caused by freezing of an account number, account number freezing information including an account number freezing term may be acquired. For example, the account freeze deadline information may be a freeze 24 hours. It may then be determined whether the freeze term is less than a preset freeze term threshold. For example, the account freeze period information is 24 hours frozen, the preset freeze period threshold is 48 hours, and the determination result is yes. If yes, the account freezing period is passed, and whether the account freezing is removed or not can be detected. For example, when the account freeze period has elapsed 24 hours, it is checked whether the account freeze has been released. If the scheduling request is released, the next scheduling retry is carried out, namely the scheduling strategy is adopted to determine the time of the next scheduling retry, and the next scheduling retry is executed when the time is reached. Therefore, under the abnormal condition that the operation processing abnormity type is caused by account freezing, the next scheduling retry is executed when the freezing time limit is determined to be smaller than the preset freezing time limit threshold value, the invalid scheduling retry performed when the freezing time limit is too long is avoided, and the efficiency of the scheduling retry is improved.

For another example, when the dependent job processing exception type is determined based on step S102, it may also be continuously determined whether the dependent job processing exception type is caused by insufficient account funds. If yes, the associated account information of the account with insufficient funds can be obtained. For example, if the current account is insufficient, account information associated with the current account is obtained. Further, the associated account is used as an object of next scheduling retry. For example, since the current account has insufficient funds and the next deduction operation is directly performed, the next deduction operation still cannot be successfully performed, and therefore, the scheduling retry is directly performed on the associated other accounts, that is, the deduction operation is performed on the other associated accounts. Therefore, when the next scheduling retry is needed, the scheduling strategy is adopted to determine the time of the next scheduling retry, and the next scheduling retry is executed when the time is up. Therefore, under the abnormal condition when the operation-dependent processing abnormal type is caused by insufficient account funds, the relevance of scheduling retry is improved by taking the associated account as the target of next scheduling retry.

According to the technical solution of the first embodiment, a processing procedure performed according to the technical solution of the first embodiment when a refund transaction processing exception occurs is described below.

Step S201, according to the specific abnormal situation when the job scheduling processing is abnormal, determining the abnormal type of the job scheduling processing.

The refund service is executed to the account of the user without success, and the abnormal condition may be caused by the account being logged off, or the account being blocked, or the account being unable to be connected due to the unstable network system, or a program being unable to be successfully called for a long time. Since account logout will cause that refund to account can not be performed, even if the refund task is performed again, the refund task still can not be successfully performed, and this kind of processing exception can not be solved by scheduling retry, which can be referred to as an exception type that can not be solved by scheduling retry. When the account is frozen by the bank account processing system, if the account is refunded, the account needs to wait and depend on the bank account processing system to unfreeze the account, and the processing exception can be classified into a type of job-dependent processing exception. Exceptions such as the inability to connect to a user's account due to network jitter are typically sporadic, infrequent, and can be quickly reprocessed, and so such processing exceptions may be referred to as a sporadic processing exception type. When calling a program or other abnormal conditions with timeout exception, the calling needs to wait for an indefinite time before calling again, and the calling may be classified as system exception or calling timeout exception.

The job scheduling processing exception that may occur may be a type of job scheduling processing exception determined according to an exception code corresponding to the detected specific exception condition. If the generated preset exception code is "00000003" when the account is detected as being unable to refund to the account due to log-out, the exception is determined as an exception which cannot be solved by scheduling retry.

Step S202, determining whether next scheduling retry is needed or not according to the determined job scheduling processing exception type; and if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type.

If the refund can not be executed because the program can not be called successfully for a long time, determining that the next scheduling retry is needed, wherein the scheduling strategy is a Fibonacci gradient strategy, namely determining the time interval of the next scheduling retry according to the Fibonacci gradient. For example, if the current call times out, such as calling a function, for 2 seconds without successful execution, the time interval for the next scheduled retry is 3 seconds. If no more execution succeeds, the time interval for the next scheduled retry is 5 seconds.

If the reason that the refund cannot be executed is that the network system is unstable and cannot be connected with the account, the next scheduling retry is determined to be needed, and the scheduling strategy is a short-time interval strategy. For example, the time interval for the next scheduled retry is 0.5 seconds.

And if the account is frozen by the bank account processing system, determining that the next scheduling retry is needed, wherein the scheduling strategy is a long time interval strategy. For example, the time interval for the next scheduled retry is 2 days.

If the account is logged off, determining that a next scheduling retry is not required, and further performing the following steps: and executing alarm operation. And reminding manual intervention by directly executing an alarm operation step, and carrying out corresponding manual processing. In addition, credit information of the user corresponding to the account can be acquired, and the credit information comprises credit level and credit score. In addition, the credit score and the credit level of the user can be further adjusted according to a preset credit management rule.

Step S203, if the next scheduling retry is needed, the scheduling policy is adopted to determine the time of the next scheduling retry, and the next scheduling retry is executed when the time is reached.

After determining the job scheduling processing exception type based on step S202, whether a next scheduling retry is required, and if yes, acquiring a scheduling policy corresponding to the job scheduling processing exception type, determining a time of the next scheduling retry by using the scheduling policy, and executing the next scheduling retry when the time arrives, specifically including the following cases:

if the refund cannot be executed due to the fact that a program cannot be called successfully for a long time, the time interval of the next scheduling retry is determined according to the Fibonacci increment sequence, and the next scheduling retry is executed when the time is reached. In order to avoid excessive consumption of system resources caused by repeated execution of scheduling retries in the case of unsuccessful scheduling retries all the time, a strategy for terminating scheduling retries may be set, and the following steps are specifically executed: it is determined whether the time for the next scheduled retry exceeds a preset time interval threshold. If not, the next scheduling retry is executed when the time arrives. For example, if the determined time interval for the next scheduled retry is less than the preset time interval threshold for 20 seconds for 5 seconds, the next scheduled retry is executed after 5 seconds. If after a number of scheduling retries, it is again determined that the time interval for a scheduling retry exceeds 20 seconds, the next scheduling retry may be terminated.

If the refund can not be executed due to the fact that the network system is unstable and cannot be connected with the account, the time of the next scheduling retry is determined according to the short time interval strategy, and the next scheduling retry is executed when the time is up. In addition, a strategy for terminating and scheduling retry based on the number of retries as termination is also set. The specific execution process comprises the following steps: firstly, counting the execution times of the time step for determining the next scheduling retry by adopting the short time interval strategy; and when the execution times do not exceed the preset time threshold, executing the next scheduling retry. For example, after each short time interval for determining the next scheduling retry, the counter (counter) is incremented by 1, and when the number of executions, for example, 5 times, is less than the preset execution threshold value 20 times, the next scheduling retry is executed. Where a counter is a counter that allows a user to create a reference anywhere in a thread group. The counter configuration allows the user to configure the maximum value (e.g. 20 times), and the counter may be set to end after cycling through 20 times.

If the refund can not be executed because the account is frozen by the bank account processing system, account freezing information can be acquired, wherein the account freezing information comprises an account freezing period. For example, the account freeze deadline information may be a freeze 24 hours. It may then be determined whether the freeze term is less than a preset freeze term threshold. For example, the preset freeze period threshold is 48 hours, when the determination is yes. If yes, the account freezing period is passed, and whether the account freezing is removed or not can be detected. For example, when the account freeze period has elapsed 24 hours, it is checked whether the account freeze has been released. If the scheduling retry is released, the next scheduling retry is carried out, namely, a long time interval scheduling strategy is adopted to determine the time of the next scheduling retry, and the next scheduling retry is executed when the time is reached. Therefore, the next scheduling retry is executed when the freezing time limit is determined to be smaller than the preset freezing time limit threshold, so that invalid scheduling retry performed when the freezing time limit is too long is avoided, and the efficiency of scheduling retry is improved.

If the refund can not be executed because the account is frozen by the bank account processing system, the related account information of the account with insufficient funds can be obtained. Further, the associated account is used as an object of next scheduling retry. For example, scheduling retries are directly performed on the other associated accounts, that is, deduction operations are performed on the other associated accounts, so that when a next scheduling retry is required, a long time interval scheduling strategy is adopted to determine the time of the next scheduling retry, and when the time arrives, the next scheduling retry is performed. Therefore, the relevance of scheduling retry is improved by taking the associated account number as the target of next scheduling retry.

Fig. 3 is a schematic structural diagram of an embodiment of a scheduling retry apparatus provided in the present application. Since the apparatus embodiments are substantially similar to the method embodiments, they are described in a relatively simple manner, and reference may be made to the corresponding description of the method embodiments provided above for relevant portions. The device embodiments described below are merely illustrative.

The retry apparatus includes: an exception type determining unit 301, a scheduling policy obtaining unit 302, and a scheduling retry unit 303.

In this embodiment, the exception type determining unit 301 is configured to determine a job scheduling processing exception type according to a specific exception condition when the job scheduling processing exception occurs; a scheduling policy obtaining unit 302, configured to determine whether a next scheduling retry is required according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and a scheduling retry unit 303, configured to determine a time of a next scheduling retry by using the scheduling policy if the next scheduling retry is required, and execute the next scheduling retry when the time arrives.

Since the embodiment of the electronic device is basically similar to the embodiment of the method, the description is relatively simple, and the related portions please refer to the corresponding description of the embodiment of the method provided above. The electronic device embodiments described below are merely illustrative.

The present application also proposes an electronic device for scheduling retries, comprising: a display; a processor; a memory for storing a program for scheduling retries, which when read executed by the processor performs the following: determining the type of the job scheduling processing exception according to the specific exception condition when the job scheduling processing exception; determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up.

The present application further provides a computer-readable storage medium, which is substantially similar to the method embodiment and therefore is described more simply, and the relevant portions please refer to the corresponding descriptions of the method embodiments provided above. The computer-readable storage medium embodiments described below are merely illustrative.

A computer-readable storage medium is also presented having a scheduled retry program stored thereon, which when read and executed by a processor, performs the following: determining the type of the job scheduling processing exception according to the specific exception condition when the job scheduling processing exception; determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining a scheduling strategy corresponding to the job scheduling processing exception type; and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up.

Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

1. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.

2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Claims

1. A method of scheduling retries, the method comprising:

determining the type of the job scheduling processing exception according to the specific exception condition when the job scheduling processing exception;

determining whether the next scheduling retry is needed or not according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining scheduling strategies corresponding to the job scheduling processing exception types, wherein each job scheduling processing exception type corresponds to one scheduling strategy; if the judgment result is no, further executing the following steps: executing alarm operation;

and if the next scheduling retry is needed, determining the time of the next scheduling retry by adopting the scheduling strategy, and executing the next scheduling retry when the time is up.

2. The scheduling retry method according to claim 1, further comprising, before determining the job scheduling processing exception type according to the specific exception condition when the job scheduling processing exception is abnormal:

after receiving an action request of an action initiator, requesting a server to verify the information of the action initiator;

after receiving the information that the information of the action initiator sent by the server passes the verification, confirming the current action request to the action initiator to be successfully executed;

and according to the action request, carrying out job scheduling of the job required by the action request.

3. The method of claim 1, wherein the job scheduling handling exception type comprises at least one of:

exceptions that cannot be resolved by scheduling retries, dependent job handling exceptions, sporadic handling exceptions, system exceptions, or call timeout exceptions.

4. The method according to claim 3, wherein if the job scheduling processing exception type is the exception that cannot be resolved by the scheduling retry, the step of determining whether the next scheduling retry is required according to the determined job scheduling processing exception type determines that the result is no.

5. The method according to claim 3, wherein if the job scheduling processing exception type is a system exception or a call timeout exception, the determination result of determining whether a next scheduling retry is required according to the determined job scheduling processing exception type is yes; the scheduling strategy is a Fibonacci gradient sequence strategy, namely, the time interval of the next scheduling retry is determined according to the Fibonacci gradient sequence.

6. The method according to claim 3, wherein if the job scheduling processing exception type is an occasional processing exception, the determination result of determining whether the next scheduling retry is required according to the determined job scheduling processing exception type is yes; the scheduling strategy short time interval strategy is that the time interval of the next scheduling retry is a short time interval.

7. The method according to claim 3, wherein if the job scheduling processing exception type is a job-dependent processing exception, the determination result of determining whether a next scheduling retry is required according to the determined job scheduling processing exception type is yes; the scheduling strategy is a long time interval strategy, namely the time interval of the next scheduling retry is a long time interval.

8. The method of claim 4, further comprising, after the performing the alarm operation:

when the abnormity which cannot be solved through the scheduling retry is determined to be caused by account logout, acquiring credit information of a user corresponding to the account, wherein the credit information comprises credit level and credit score;

and adjusting the credit score and the credit level of the user according to a preset credit management rule.

9. The method of claim 5, wherein the determining the time of the next scheduling retry by the scheduling policy and executing the next scheduling retry when the time arrives are specifically:

determining the time of the next scheduling retry by adopting the Fibonacci delivery strategy;

determining whether the time of the next scheduling retry determined according to the Fibonacci gradient sequence exceeds a preset time interval threshold;

if not, the next scheduling retry is executed when the time arrives.

10. The method of claim 6, wherein the determining the time of the next scheduling retry by the scheduling policy and executing the next scheduling retry when the time arrives are specifically:

determining the time of next scheduling retry by adopting the short time interval strategy;

counting the execution times of the time step for determining the next scheduling retry by adopting the short time interval strategy;

and when the execution times do not exceed the preset time threshold, executing the next scheduling retry.

11. The method of claim 7, further comprising, prior to said determining a time for a next scheduled retry using the scheduling policy:

when determining that the dependent job processing exception type is caused by account freezing, acquiring account freezing information, wherein the account freezing information comprises an account freezing period;

determining whether the freezing time limit is smaller than a preset freezing time limit threshold value;

if yes, executing the next step.

12. The method of claim 11, wherein after determining whether the freeze period is less than a preset freeze period threshold, prior to the step of performing the next step, further comprising:

when the account freezing period is over, detecting whether the account freezing is removed;

if yes, executing the next step.

13. The method of claim 7, further comprising, before determining the time for the next scheduled retry using the scheduling policy:

when determining that the operation-dependent processing exception type is caused by account fund shortage, acquiring associated account information of the account with insufficient fund;

and taking the associated account as an object of next scheduling retry.

14. The method of claim 1, wherein the job scheduling handling exception is generated at the following stage:

a local data processing phase or/and a remote system processing phase is invoked.

15. The method of claim 3, wherein the type of sporadic processing exceptions includes network jitter induced processing exceptions.

16. An apparatus for scheduling retries, the apparatus comprising:

the abnormal type determining unit is configured for determining the abnormal type of the job scheduling processing according to the specific abnormal condition when the job scheduling processing is abnormal;

the scheduling strategy obtaining unit is configured to determine whether to perform next scheduling retry according to the determined job scheduling processing exception type; if the judgment result is yes, further obtaining scheduling strategies corresponding to the job scheduling processing exception types, wherein each job scheduling processing exception type corresponds to one scheduling strategy;

the scheduling retry unit is configured to determine the time of the next scheduling retry by adopting the scheduling strategy if the next scheduling retry is required, and execute the next scheduling retry when the time is up;

the scheduling retry apparatus further includes:

an execution unit, configured to, if the determination result is negative, execute the following steps: and executing alarm operation.

17. The scheduled retry apparatus of claim 16, wherein the apparatus further comprises:

the verification request unit is configured to request the server to verify the information of the action initiator after receiving the action request of the action initiator;

the confirmation unit is configured to confirm that the current action request is successfully executed to the action initiator after receiving the information that the information of the action initiator sent by the server passes the verification;

and the scheduling unit is configured to perform job scheduling of the job required by the action request according to the action request.

18. The apparatus according to claim 16, wherein if the job scheduling processing exception type is an exception that cannot be resolved by a scheduling retry, the step of determining whether a next scheduling retry is required based on the determined job scheduling processing exception type determines that the result is no.

19. The apparatus according to claim 16, wherein the scheduling policy obtaining unit is further configured to determine whether a next scheduling retry is required according to the determined job scheduling processing exception type if the job scheduling processing exception type is a system exception or a call timeout exception; the scheduling strategy is a Fibonacci gradient sequence strategy, namely, the time interval of the next scheduling retry is determined according to the Fibonacci gradient sequence.

20. The apparatus according to claim 16, wherein the scheduling policy obtaining unit is further configured to determine whether a next scheduling retry is required according to the determined job scheduling processing exception type if the job scheduling processing exception type is an occasional processing exception; the scheduling strategy short time interval strategy is that the time interval of the next scheduling retry is a short time interval.

21. The apparatus according to claim 16, wherein the scheduling policy obtaining unit is further configured to determine whether a next scheduling retry is required according to the determined job scheduling processing exception type if the job scheduling processing exception type is a dependent job processing exception; the scheduling strategy is a long time interval strategy, namely the time interval of the next scheduling retry is a long time interval.

22. The scheduled retry apparatus of claim 17, wherein the apparatus further comprises:

the credit information acquisition unit is configured to acquire credit information of a user corresponding to an account when the abnormity which cannot be solved through the scheduling retry is determined to be caused by the cancellation of the account, and the credit information comprises credit level and credit score;

and the credit information adjusting unit is configured for adjusting the credit score and the credit level of the user according to a preset credit management rule.

23. The apparatus of claim 18, wherein the scheduling retry unit is specifically configured to:

determining the time of next scheduling retry by adopting a Fibonacci delivery strategy;

if not, the next scheduling retry is executed when the time arrives.

24. The apparatus of claim 19, wherein the scheduling retry unit is specifically configured to:

determining the time of next scheduling retry by adopting a short time interval strategy;

25. The scheduled retry apparatus of claim 20, wherein the apparatus further comprises,

the account freezing information acquisition unit is configured to acquire account freezing information when determining that the type of the job-dependent processing abnormality is caused by account freezing, wherein the account freezing information comprises an account freezing deadline;

the freezing time limit judging unit is configured for determining whether the freezing time limit is smaller than a preset freezing time limit threshold value; if yes, determining to execute the next step.

26. The scheduled retry apparatus of claim 25, wherein the apparatus further comprises:

the detection unit is configured to detect whether account freezing is removed or not when the account freezing period passes; if yes, determining to execute the next step.

27. The scheduled retry apparatus of claim 20, wherein the apparatus further comprises,

the system comprises a related account information acquisition unit, a processing unit and a processing unit, wherein the related account information acquisition unit is configured to acquire related account information of an account with insufficient funds when determining that the dependence on the operation processing exception type is caused by insufficient funds of the account;

and the scheduling retry object determining unit is configured to use the associated account number as an object of the next scheduling retry.

28. An electronic device for scheduling retries, the electronic device comprising:

a display;

a processor;

a memory for storing a program for scheduling retries, which when read executed by the processor performs the following:

29. A computer-readable storage medium having a scheduled retry program stored thereon, the program when read and executed by a processor performing the operations of: