Task execution method, device, equipment and product

Abstract

The invention discloses a task execution method, device, equipment and product, and relates to the technical field of task scheduling, the method is applied to a distributed task scheduling system, the distributed task scheduling system comprises an operation platform and a configuration platform, and the method comprises the following steps: receiving a to-be-executed task sent by a user side, the to-be-executed task is selected by the user side through a visual interface; performing configuration loading on the to-be-executed task through the configuration platform to obtain a configuration task set; the configuration task set is sent to the user side, and the user side sends a starting instruction to the distributed task scheduling system based on the configuration task set; and based on the starting instruction, executing the configuration task set through the operation platform to obtain a task execution result. Therefore, the problem that in the prior art, due to the fact that a distributed task scheduling platform is tedious in operation process and has a certain use threshold, the efficiency is not high in actual use is solved.

Description

Technical Field

[0001] This application relates to the field of task scheduling technology, and in particular to a task execution method, apparatus, device, and product. Background Technology

[0002] XXL-Job is a distributed scheduled task platform widely used in enterprise business systems. It is mainly used to schedule and manage scheduled tasks. Currently, developers mainly rely on the XXL-Job management backend to manage XXL-Job tasks. When performing routine task management operations such as starting, stopping, or adding tasks, they need to log in to the management backend system first, then enter the corresponding task management page, and then complete each operation step by step according to the preset fixed process. This task management mode based on the management backend is the XXL-Job task management solution commonly used in the industry.

[0003] However, the above-mentioned method of performing tasks through the management backend has obvious shortcomings. On the one hand, the operation process is relatively cumbersome, requiring multiple page jumps and multiple clicks for each task operation. Especially in scenarios where multiple tasks need to be frequently operated, it will consume a lot of time and energy of developers and seriously affect work efficiency. On the other hand, for developers who are not familiar with the operation process of the XXL-Job management backend, they need to spend extra time learning and familiarizing themselves with the operation steps, which not only increases the threshold for use, but also reduces the overall task processing efficiency of the team to a certain extent.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main purpose of this application is to provide a task execution method, apparatus, device and product, which aims to solve the technical problem that the operation process of the existing distributed task scheduling platform is cumbersome and there is a certain threshold for use, resulting in low efficiency in actual use.

[0006] To achieve the above objectives, this application proposes a task execution method applied to a distributed task scheduling system. The distributed task scheduling system includes an operating platform and a configuration platform. The task execution method includes: Receive tasks to be executed sent by the user terminal, which are selected by the user terminal through a visual interface; The configuration platform is used to load the configuration of the tasks to be executed, thereby obtaining a set of configuration tasks; The configuration task set is sent to the user terminal, and the user terminal sends a start command to the distributed task scheduling system based on the configuration task set. Based on the startup command, the configured task set is executed through the operating platform to obtain the task execution result.

[0007] In one embodiment, before the step of receiving the task to be executed sent by the user terminal, the method further includes: Receive login requests sent by the user client; The login request is parsed to obtain the login key, and the user parameters are loaded using the login key. Based on the user parameters, user permission information and a list of executable tasks are loaded. A visual interface is generated based on the user permission information and the list of executable tasks, allowing the user to select tasks.

[0008] In one embodiment, the step of configuring and loading the task to be executed through the configuration platform to obtain a configuration task set includes: Based on the task to be executed, the task ID of the task to be executed is determined by the operating platform; Based on the task ID, the selected task is confirmed through the configuration platform to obtain a set of selected task IDs; The set of selected task IDs is sent to the user terminal, and the user terminal sends a configuration command to the distributed task scheduling system after confirming that the set of selected task IDs is correct. According to the configuration instructions, the set of selected task IDs is written into the configuration file through the configuration platform to obtain the configuration task set.

[0009] In one embodiment, the step of executing the configured task set through the operating platform based on the startup command to obtain the task execution result includes: Based on the configured task set, the operation task ID set is obtained by querying the configuration platform. The task ID set is sent to the user terminal, and the user terminal, after confirming that the task ID set is correct, sends a confirmation command to the distributed task scheduling system. Upon receiving the confirmation instruction, the task parameters are obtained by traversing the set of operation task IDs through the operation platform; The operation task ID set is executed based on the task parameters to obtain the task execution result.

[0010] In one embodiment, after the step of configuring and loading the task to be executed through the configuration platform to obtain a configuration task set, the method further includes: Receive the task addition instruction sent by the user terminal; Based on the task addition instruction, load the new task session box through the operation platform; The new task session box is sent to the user terminal, and the user terminal adds the new task parameters to the new task session box and then sends the new instruction to the distributed task scheduling system; The system performs a task addition determination based on the newly added task parameters and the authentication token from the user terminal. If the judgment result is successful, a success message will be sent to the user terminal through the new task dialog box.

[0011] Furthermore, to achieve the above objectives, this application also proposes a task execution method, which is applied to a user terminal and includes: Select the task to be executed through the visual interface; The tasks to be executed are sent to the distributed timed task scheduling system, which loads the configuration through the configuration platform to obtain a set of configured tasks. Receive the set of configured tasks sent by the distributed task scheduling system; Based on the configured task set, a start command is sent to the distributed task scheduling system. The distributed task scheduling system then executes the configured task set through the operating platform based on the start command, and obtains the task execution result.

[0012] In one embodiment, after the step of sending a start command to the distributed task scheduling system based on the configured task set, the method further includes: The system receives execution status information of the configured task set sent by the distributed task scheduling system. The execution status information includes task execution progress, task execution status identifier, and exception prompt information. The visualization interface is used to construct a status display area, which displays the execution status information according to the task ID. When a failed task is detected, a pop-up window is generated with retry options, log viewing options, and task editing options. Receive the target operation command triggered by the user based on the operation pop-up window; If the target operation instruction is a retry instruction, the corresponding failed task ID will be resent to the distributed task scheduling system. If the target operation instruction is a log viewing instruction, then the task execution log returned by the distributed task scheduling system is obtained and displayed in the visualization interface pop-up window; If the target operation command is a task editing command, the user will be redirected to the task parameter editing interface to modify the task parameters.

[0013] Furthermore, to achieve the above objectives, this application also proposes a task execution device applied to a distributed task scheduling system, the distributed task scheduling system including an operating platform and a configuration platform, the task execution device comprising: The receiving module is used to receive tasks to be executed sent by the user terminal, which are selected by the user terminal through a visual interface; The configuration module is used to load the configuration of the task to be executed through the configuration platform to obtain a configuration task set; The sending module is used to send the configuration task set to the user terminal, and the user terminal sends a start command to the distributed task scheduling system based on the configuration task set; The execution module is used to execute the configured task set through the operating platform based on the startup command, and obtain the task execution result.

[0014] In addition, to achieve the above objectives, this application also proposes a task execution device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the task execution method as described above.

[0015] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and which, when executed by a processor, implements the steps of the task execution method described above.

[0016] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the task execution method described above.

[0017] One or more technical solutions proposed in this application have at least the following technical effects: This application proposes a task execution method, apparatus, device, and product. The method is applied to a distributed task scheduling system, which includes an operation platform and a configuration platform. The method involves receiving tasks to be executed from a user terminal, selected by the user terminal through a visual interface; configuring and loading the tasks to be executed through the configuration platform to obtain a configuration task set; sending the configuration task set to the user terminal, which then sends a start command to the distributed task scheduling system based on the configuration task set; and executing the configuration task set through the operation platform based on the start command to obtain the task execution result. Thus, selecting tasks directly through a visual interface eliminates the cumbersome multi-page navigation; automatically loading task configurations and generating configuration task sets through the configuration platform simplifies the manual configuration process; and executing tasks only after user terminal confirmation lowers the learning curve. Finally, the operation platform efficiently executes tasks, solving the problem of cumbersome operation processes and high learning curves in existing distributed task scheduling platforms, which lead to low efficiency in actual use, thereby improving task execution efficiency. Attached Figure Description

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

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating an embodiment of the task execution method of this application. Figure 2 This is a flowchart illustrating Embodiment 2 of the task execution method of this application; Figure 3 This is a schematic diagram of the visual interface involved in the task execution method of this application; Figure 4 This is a schematic diagram illustrating the error parameters involved in the task execution method of this application; Figure 5 A simplified flowchart illustrating the task execution method provided in Embodiment 2 of this application; Figure 6 This is a schematic diagram of the module structure of the task execution device according to an embodiment of this application; Figure 7 This is a schematic diagram of the device structure of the hardware operating environment involved in the task execution method in the embodiments of this application.

[0021] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0022] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0023] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0024] The main solution of this application embodiment is as follows: receiving a login request sent by a user terminal; parsing the login request to obtain a login key, and loading user parameters using the login key; loading user permission information and an executable task list based on the user parameters; generating a visual interface based on the user permission information and the executable task list for the user terminal to select tasks. Based on the task to be executed, the operation platform determines the task ID of the task to be executed; based on the task ID, the configuration platform confirms the selection of tasks, obtaining a set of selected task IDs; the set of selected task IDs is sent to the user terminal, and the user terminal, after confirming that the set of selected task IDs is correct, sends a configuration command to the distributed task scheduling system; according to the configuration command, the configuration platform writes the set of selected task IDs into a configuration file, obtaining a configuration task set. Based on the configured task set, an operation task ID set is obtained by querying the configuration platform; the task ID set is sent to the user terminal, and the user terminal, after confirming that the operation task ID set is correct, sends a confirmation command to the distributed task scheduling system; upon receiving the confirmation command, the operation platform iterates through the operation task ID set to obtain task parameters; the operation task ID set is executed based on the task parameters to obtain the task execution result. A task addition command is received from the user terminal; based on the task addition command, a new task session box is loaded through the operation platform; the new task session box is sent to the user terminal, where the user terminal adds the new task parameters to the new task session box and then sends an addition command to the distributed task scheduling system; the new task parameters and the user terminal's authentication token are used to determine if the task addition is successful; if the determination result is successful, a success message is sent to the user terminal through the new task session box. Select a task to be executed through a visual interface; send the task to be executed to a distributed timed task scheduling system, which loads the configuration through a configuration platform to obtain a configuration task set; receive the configuration task set sent by the distributed task scheduling system; send a start command to the distributed task scheduling system based on the configuration task set, which then executes the configuration task set through the operation platform based on the start command to obtain the task execution result.The system receives execution status information of the configured task set sent by the distributed task scheduling system. This execution status information includes task execution progress, task execution status identifier, and exception prompts. A status display area is constructed through the visual interface, displaying the execution status information according to task IDs. When a failed task is detected, a pop-up window with retry, log viewing, and task editing options is generated. The system receives a target operation command triggered by the user based on the pop-up window. If the target operation command is a retry command, the corresponding failed task ID is resent to the distributed task scheduling system. If the target operation command is a log viewing command, the task execution log returned by the distributed task scheduling system is obtained and displayed through the visual interface pop-up window. If the target operation command is a task editing command, the user is redirected to the task parameter editing interface to modify the task parameters. This solves the problem of cumbersome operation processes and a certain usage threshold in existing distributed task scheduling platforms, leading to low efficiency in actual use. It achieves task execution and improves task execution efficiency. Based on the solution of this invention, addressing the problem that real-world distributed timed task scheduling platforms have cumbersome operation processes, requiring multiple page jumps and clicks for each task operation, especially when multiple tasks need to be frequently operated, which consumes a lot of time and energy and requires time to learn and become familiar with the operation steps, increasing the usage threshold and resulting in low efficiency, this invention designs a task execution method. The effectiveness of the task execution method of this invention is verified when executing tasks, and finally, the efficiency of task execution using the method of this invention is significantly improved.

[0025] In this embodiment, for ease of description, the task execution device will be used as the execution subject in the following description.

[0026] XXL-Job, a distributed scheduled task platform, is widely used in enterprise business systems for scheduling and managing scheduled tasks. Currently, developers primarily rely on the XXL-Job management backend to manage XXL-Job tasks. For routine task management operations such as starting / stopping or adding tasks, developers must first log in to the management backend system, then access the corresponding task management page, and follow a pre-defined workflow to complete each step. This backend-based task management model is the most common XXL-Job task management solution in the industry. However, this backend-based approach has significant drawbacks, one being the cumbersome workflow. A single task operation may require multiple page jumps and numerous clicks. The interaction between clicks and the overlapping of multiple fixed operation steps can lead to a decrease in task management efficiency. Another issue is the learning curve; when developers have different operational experience, their ability to complete task management will be affected by their familiarity with the operation. If they are not familiar with the backend process, the efficiency of task execution will also decrease significantly. Furthermore, there is the issue of batch operation adaptation. Precise and efficient task management needs to adapt to scenarios with frequent multi-task operations. However, in daily enterprise management, some scenarios have high task operation frequency and large quantity, and special data processing requirements, which also affects the efficiency of task management. Therefore, the current XXL-Job task management also encounters challenges in scenario adaptability. Since different enterprises have different task scales, operation frequencies, team familiarity, etc., if the task management model is not optimized for specific scenarios, efficiency will also decrease.

[0027] This application provides a solution in a distributed task scheduling system that includes an operating platform and a configuration platform. Tasks to be executed can be directly selected through a visual interface, eliminating the cumbersome process of multiple page navigation. The configuration platform automatically loads task configurations and generates configuration task sets, simplifying the manual configuration process. Tasks are executed only after user confirmation, lowering the learning curve. Finally, tasks are executed efficiently through the operating platform. This solution addresses the problem of cumbersome operating procedures and high learning curves in existing distributed task scheduling platforms, which lead to low efficiency in practical use, thus improving task execution efficiency.

[0028] Based on this, embodiments of this application provide a task execution method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the task execution method of this application.

[0029] In this embodiment, the task execution method is applied to a distributed task scheduling system, which includes an operating platform and a configuration platform. The task execution method includes steps S01 to S04: Step S01: Receive the task to be executed sent by the user terminal, wherein the task to be executed is selected by the user terminal through a visual interface; Before describing the solution in this embodiment, it should be clear that XXL-Job, as a distributed scheduled task platform, is widely used in enterprise business systems. Its core function is the scheduling and management of scheduled tasks. Currently, the industry generally adopts a management backend mode for task management. Developers need to log in to the backend, enter the corresponding task management page, and complete the tasks such as starting, stopping, and adding tasks step by step according to a fixed process. However, this method has obvious shortcomings. On the one hand, the operation process is cumbersome. Each task operation requires multiple page jumps and multiple clicks. Especially in scenarios with frequent multi-task operations, it will consume a lot of time and energy of developers and seriously affect work efficiency. On the other hand, the usage threshold is high. Developers who are not familiar with the backend operation process need to spend extra time learning, which not only increases the difficulty of individual use, but also reduces the overall task processing efficiency of the team to a certain extent.

[0030] Therefore, in order to solve the above problems, this embodiment uses a distributed task scheduling system, including an operating platform and a configuration platform, to receive tasks to be executed sent by the user. The tasks to be executed are selected by the user through a visual interface, which is integrated into the development tool and seamlessly connected with the development environment. Users do not need to switch to a separate management backend; they can quickly select and initiate tasks within the same interface used in their daily coding work. Specifically, users can find the task operation entry point in convenient locations such as the sidebar, toolbar, or right-click menu of the development tool. Through intuitive methods such as clicking, dragging, or keyword search, users can select the required task type and specific parameters from a preset task template library or a historical task list. The entire process does not require memorizing complex backend paths and operation steps, greatly simplifying the pre-process of task initiation.

[0031] Step S02: The configuration platform is used to load the configuration of the task to be executed to obtain a configuration task set; Upon receiving a task to be executed from the user, the system loads the configuration for the task through the integrated configuration platform, resulting in a configuration task set. This platform features dynamic parameter parsing and task rule adaptation capabilities, automatically matching the corresponding configuration template based on the task type (e.g., scheduled tasks, event-triggered tasks, dependency chain tasks). For example, for scheduled tasks, the platform loads a time expression parsing module, supporting parameter configuration for various timing strategies such as CRON expressions, fixed intervals, and delayed execution. Users can directly set key information such as the task's execution cycle, start time, and end conditions through a visual interface. For dependency chain tasks, the platform calls a task dependency management component, allowing users to intuitively define the execution order, retry dependencies, and resource sharing rules between tasks by dragging and dropping task nodes onto the canvas and connecting arrows. It also automatically verifies the legality of dependency chains to prevent circular dependencies or isolated task nodes.

[0032] Step S03: The configuration task set is sent to the user terminal, and the user terminal sends a start command to the distributed task scheduling system based on the configuration task set; Once the configuration task set is obtained, it is sent to the user terminal, where it is checked or confirmed. After confirmation, a start command is sent back to the distributed task scheduling system. The user terminal displays detailed information about the configuration task set in the form of a visual list or flowchart, including task name, type, configuration parameters, and dependencies. The user can check the parameters item by item to see if they meet expectations. If an error is found, the user can directly initiate a modification request in the interface. The system will then redirect to the configuration platform to adjust the parameters. The adjusted configuration task set will be pushed back to the user terminal for verification. If the verification is correct, the user can click the "Start Task" button to generate a start command. This command contains a unique task identifier, a start timestamp, and the user's confirmation signature. It is transmitted to the task receiving module of the distributed task scheduling system through an encrypted channel to ensure the security and integrity of the command during transmission.

[0033] Step S04: Based on the startup command, execute the configured task set through the operating platform to obtain the task execution result.

[0034] Finally, the distributed task scheduling system can execute the configured task set through the operation platform based on the start command, thereby obtaining the task execution results. Upon receiving the start command, the operation platform first decrypts and verifies it, including verifying the validity of the task's unique identifier, the rationality of the start timestamp, and the legality of the user's confirmation signature. After successful verification, it parses the execution sequence, resource requirements, and runtime parameters of each subtask from the configured task set. Subsequently, the operation platform constructs a directed acyclic graph (DAG) based on the task dependencies and, according to the task type and resource consumption, distributes the subtasks to different execution nodes in the cluster using a load balancing algorithm. Upon receiving a subtask, the execution node calls the corresponding executor to load the required runtime environment (such as specific software versions, dependency libraries, etc.) and executes the specific operations according to the configuration parameters. During task execution, the operation platform monitors the running status of each subtask in real time, maintains communication with the execution nodes through a heartbeat mechanism, and collects key indicators including CPU utilization, memory usage, network I / O, and task progress. This monitoring data is then fed back to the monitoring module of the distributed task scheduling system in real time and displayed to the user in the form of a visual dashboard.

[0035] Specifically, before step S01 above, which involves receiving the task to be executed sent by the user terminal, the method further includes: Step S0101: Receive a login request sent by the user client; Step S0102: Parse the login request to obtain the login key, and load the user parameters using the login key; Step S0103: Based on the user parameters, load the user permission information and the list of executable tasks. Step S0104: Generate a visual interface based on the user permission information and the list of executable tasks, so that the user can select tasks.

[0036] First, the program receives the login information entered by the user on the page. At the same time, when the program starts, it first checks whether the preset account and password configuration file exists. If it exists, it automatically decrypts the encrypted account and password information and displays it back to the login interface. The password field is displayed with "*" to mask the password. The login request carries the above login information.

[0037] Then, the login request is parsed to obtain the login key. The login key contains the username and password entered by the user or loaded from the configuration file (if it is encrypted, it is first decrypted using the encryption algorithm configured in the authentication module). The authentication module sends the login key to the login interface of the XXL-Job management backend through the Requests library to initiate verification. After the XXL-Job management backend completes the identity verification, it returns a login success response and session information (such as Cookie or Token). The system saves this session information as the core login key component. At the same time, based on the session information, it requests the XXL-Job management backend to load user parameters (such as user ID, department, role identifier, etc.), realizing the association and binding of the login key with the user's basic information (such as Cookie or Token). The system saves this session information and requests the XXL-Job management backend to load user parameters (such as user ID, department, role identifier, etc.) based on the session information.

[0038] Next, based on the user parameters and session information obtained in the above steps, the system loads the corresponding user permission information (such as task viewing permission, start / stop permission, and add permission) from the permission management module through user parameters (such as role identifier). On the other hand, it uses the valid session information saved by the authentication module to request the task list data that the user can operate from the XXL-Job management backend, ensuring that the loaded task list strictly matches the user's actual permissions. At the same time, the system adds a permission level filtering mechanism to additionally mark the permission level of high-permission tasks (such as batch task operations), providing a basis for subsequent interface display and operation control.

[0039] Finally, during the interface generation process, combining the security design of the authentication module with user experience optimization, user permission information and the list of executable tasks are visually linked and displayed. For example, the task list is color-coded or grouped according to permission levels, tasks without operation permissions are grayed out and the operation buttons are hidden. At the same time, the password and account display desensitization design of the login interface is retained. If the user logs in again later, they can still enjoy the convenience of automatic loading of configuration files and password "*" display. The generated visual interface not only achieves intuitive task selection, but also ensures the compliance and security of task operation through the integration of permission and security mechanisms.

[0040] More specifically, step S02 above, which involves configuring and loading the tasks to be executed through the configuration platform to obtain a set of configuration tasks, includes: Step S021: Determine the task ID of the task to be executed through the operation platform according to the task to be executed; Step S022: Based on the task ID, confirm the selected task through the configuration platform to obtain a set of selected task IDs; Step S023: The selected task ID set is sent to the user terminal, and the user terminal sends a configuration command to the distributed task scheduling system after confirming that the selected task ID set is correct. Step S024: According to the configuration instructions, the set of selected task IDs is written into the configuration file through the configuration platform to obtain the configuration task set.

[0041] After the user selects a task to be executed through the visual interface, the operation platform uses the quick filtering function of the configuration module to accurately locate the target task in the task list based on the task name, business group, and other information selected by the user. The configuration module supports a combination of keyword fuzzy search and category filtering to help users quickly find the scheduled tasks they are interested in, avoiding searching through a large number of tasks one by one. The operation platform automatically extracts and determines the unique task ID of the corresponding task to be executed based on the filtering results, providing a basic identifier for subsequent configuration operations.

[0042] In addition, the configuration platform provides a "Select Task ID" input box as the core operation carrier. Users can form a set of tasks to be operated based on the task IDs determined in the above steps in two ways: First, they can directly select the target task in the task list, and the system will automatically synchronize the IDs of the selected tasks to the "Select Task ID" input box in a comma-separated format. Second, they can manually enter the task ID in the input box (multiple IDs should be separated by commas). The configuration module verifies the validity and format of the input ID in real time. After the verification is passed, the selection of tasks is confirmed, and finally a set of selected task IDs containing all task IDs to be configured is generated.

[0043] The configuration platform synchronizes the selected task ID set to the user's visual interface and clearly displays it in the "Selected Task ID" input box of the configuration module for the user to make a final check. The user can intuitively view the completeness and accuracy of the ID set. If any adjustments are needed, the user can directly edit the input box or return to the task list to reselect the IDs. Once the user confirms that everything is correct, they can send a configuration command to the distributed task scheduling system by clicking the operation button on the interface, thus realizing a closed loop of interaction and confirmation between the user and the system.

[0044] Finally, upon receiving the configuration command, the configuration platform triggers the "Configure" button function of the configuration module, persistently writing the selected task ID set to the local configuration file. Simultaneously, the configuration module automatically synchronizes the persistent task IDs to the "Local Configuration Task ID" input box for display, achieving visual retention of the configuration results. If the configuration needs to be reused later, the user can click the "Reset" button to directly overwrite the persistent content in the "Local Configuration Task ID" input box with the content in the "Selected Task ID" input box, avoiding the tedious operation of repeatedly configuring task IDs. Ultimately, the completed configuration file is the configuration task set containing persistent task IDs, providing a stable configuration basis for subsequent task execution.

[0045] Further, step S04 above, which involves executing the configuration task set through the operating platform based on the startup command to obtain the task execution result, includes: Step S041: Based on the configured task set, obtain the operation task ID set through the configuration platform; Step S042: The task ID set is sent to the user terminal, and the user terminal sends a confirmation instruction to the distributed task scheduling system after confirming that the task ID set is correct. Step S043: After receiving the confirmation instruction, the task parameters are obtained by traversing the set of operation task IDs through the operation platform; Step S044: Execute the operation task ID set based on the task parameters to obtain the task execution result.

[0046] First, the configuration platform reads the persistent task ID information in the configuration task set, and links with the task query function of the operation module. Based on the valid session information saved by the authentication module, it constructs a query HTTP request containing the task ID. This request is sent to the task information interface of the XXL-Job management backend through the Requests library. After the backend parses the request, it returns basic information such as the status of the corresponding task and the node it belongs to. The configuration platform combines the returned information to perform a second validity check on the task ID (removing invalid or non-existent IDs), and finally forms an accurate set of operation task IDs to avoid invalid IDs affecting the subsequent execution process.

[0047] The configuration platform then synchronizes the verified set of operation task IDs to the user's visual interface, displaying auxiliary information such as the task name and current status corresponding to each task ID to help users verify intuitively. Users can quickly confirm the completeness and necessity of the task set. If adjustments are needed, they can return to the configuration stage to edit again. After confirming that everything is correct, the user sends a confirmation command by clicking the operation button on the interface. The command carries the user's confirmation identifier to ensure the accuracy of the operation and consistency with the user's intention.

[0048] Subsequently, the operation platform receives a confirmation instruction, triggering the task parameter acquisition logic of the operation module. It iterates through the set of operation task IDs in sequence. For each task ID, the operation module calls the details interface of the XXL-Job management backend again to obtain task parameters containing key information such as task execution script, scheduling cycle, number of retries, and running node. At the same time, the operation module performs format standardization processing on the obtained parameters, converting the heterogeneous data returned by different interfaces into a unified format, providing standardized input for subsequent batch execution operations and improving execution efficiency.

[0049] Finally, the operation module constructs batch execution HTTP requests based on the user's preset operation type (start or stop) and standardized task parameters. The requests carry authentication session information and operation task ID sets. After the requests are sent to the corresponding task start / stop interface in the XXL-Job management backend through the Requests library, the operation module starts the execution progress monitoring mechanism. A progress session pop-up window appears on the user's visual interface, displaying the execution status of each task in real time (such as "Executing", "Success", "Failure") and the overall progress percentage. After the XXL-Job management backend completes all task operations, it returns a summary result. After parsing the result, the operation module displays the execution details of each task (including the reasons for success / failure) in the operation feedback display area. If there are any failed tasks, the failure reason is automatically marked and a retry entry is provided, ultimately forming a complete task execution result.

[0050] Furthermore, after step S02 above, in which the configuration platform loads the configuration of the task to be executed to obtain the configuration task set, the method further includes: Step S0201: Receive the task addition instruction sent by the user terminal; Step S0202: According to the task addition instruction, load the new task session box through the operation platform; Step S0203: The new task session box is sent to the user terminal, and the user terminal adds the new task parameters to the new task session box and then sends the new instruction to the distributed task scheduling system. Step S0204: Perform a task addition judgment on the newly added task parameters and the authentication token of the user terminal; Step S0205: If the judgment result is successful, send a success message to the user terminal through the new task dialog box.

[0051] First, the system receives task addition instructions from the user client. The instructions can be triggered through multiple entry points on the user client's visual interface, such as clicking the "Add Task" button, right-clicking the task list and selecting "Add Subtask", or using a shortcut key to activate the add function. The system also records the instruction initiation time and user ID, providing basic information for subsequent operation traceability and permission verification, ensuring that the source of the instructions is traceable and the operation behavior is traceable.

[0052] Then, the operation platform responds to the task addition command and loads the preset new task dialog box. The dialog box adopts a modular layout design. In addition to basic fields such as task name, scheduling period, executor, and task parameters, it also integrates intelligent configuration components and provides industry-standard task templates (such as database backup templates and log cleanup templates). Users can directly select a template to quickly fill in the basic parameters. It also supports field linkage. For example, when the "CRON expression" scheduling type is selected, the CRON expression generator will automatically pop up, simplifying the parameter configuration process.

[0053] After the new task dialog box is synchronized to the user's client, the user can complete the parameter entry in the visual interface. The dialog box has a built-in real-time validation mechanism to instantly verify parameters such as the uniqueness of the task name, the format of the CRON expression, and the availability of the executor. If the parameters do not meet the requirements, a user-friendly prompt will pop up (such as "The task name already exists, please modify it" or "CRON expression format error, example: 0 0 2 * * ?"). After the user completes the parameter entry and confirms that it is correct, they can click the "Submit" button in the dialog box to send the new task command, which carries the complete parameters of the new task and the user's operation identifier.

[0054] Next, the new task parameters and user authentication token are extracted from the new instruction and subjected to dual verification. In terms of parameter verification, in addition to basic format verification, business rule verification is performed (such as whether the scheduling cycle conflicts with existing tasks and whether the task parameters meet the executor's operating requirements). In terms of authentication token verification, the validity, expiration date, and task addition permissions of the user associated with the token are verified (such as only administrators can add cross-department tasks). Dual verification forms a security barrier to prevent system anomalies caused by illegal operations and invalid parameters.

[0055] When the dual verification result is successful, the system completes the task addition and generates a unique task ID. A success message is sent to the user through the task addition dialog box. The message includes the task ID, task name, and subsequent operation entry (e.g., "Task addition successful! Task ID: T20251209001, click 'View Task' to jump to the details page / 'Continue Adding' to add the next task"). If the user selects "View Task", they will be automatically redirected to the task details page. If they select "Continue Adding", the dialog box parameters will be cleared and the previous configuration template will be retained, improving the efficiency of batch addition and forming an operation loop.

[0056] This embodiment, through the above-described scheme, specifically receives tasks to be executed sent by the user terminal, which are selected by the user terminal through a visual interface; the configuration platform loads the configuration of the tasks to be executed to obtain a configuration task set; the configuration task set is sent to the user terminal, which then sends a start command to the distributed task scheduling system based on the configuration task set; based on the start command, the operation platform executes the configuration task set to obtain the task execution result. Thus, by directly selecting tasks to be executed through a visual interface, the cumbersome operation of multiple page jumps is eliminated; the configuration platform automatically loads task configurations and generates configuration task sets, simplifying the manual configuration process; and the task is executed only after user terminal confirmation, lowering the learning curve; and finally, the operation platform efficiently executes tasks, solving the problem of cumbersome operation processes and certain usage barriers in existing distributed task scheduling platforms, leading to low efficiency in actual use, and improving task execution efficiency.

[0057] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 The task execution method is also applied to the user terminal, and the task execution method includes steps S05~S08: Step S05: Select the task to be executed through the visual interface; Step S06: The task to be executed is sent to the distributed timed task scheduling system, which loads the configuration through the configuration platform to obtain the configuration task set. Step S07: Receive the configuration task set sent by the distributed task scheduling system; Step S08: A start command is sent to the distributed task scheduling system based on the configured task set. The distributed task scheduling system then executes the configured task set through the operating platform based on the start command to obtain the task execution result.

[0058] It should be clear that the visual interface in this embodiment is as follows: Figure 3 As shown, the interface includes columns for task ID, description, status, Cron expression, responsible person, and operation. Users can directly select target tasks using checkboxes. The interface also integrates a "show only checkboxes" filter and a task description keyword search box, allowing users to quickly locate scheduled tasks of interest (such as tasks related to "AI products"). In addition, a new history selection memory function has been added, which automatically records tasks recently selected by the user and places them at the top of the list, reducing repetitive search operations and improving task selection efficiency.

[0059] After the user selects the tasks to be performed, the system automatically synchronizes the IDs of the selected tasks to the system. Figure 3 The “Select Task ID” input box shown (multiple IDs are separated by commas) allows the configuration platform to verify the format and validity of the IDs in the input box after receiving the task information. It also links to the historical configurations in the “Local Configuration Task ID” input box. If duplicate IDs exist, a pop-up window will prompt the user to confirm whether to merge them. At the same time, it supports automatically supplementing basic configuration parameters according to task type (such as the default executor for “AI Product Library” type tasks), and finally generates a configuration task set containing complete configuration information.

[0060] After the user receives the configuration task set, in such a way... Figure 3 The "Select Task ID" input box clearly displays all task IDs to be executed for users to verify. The interface allows users to quickly jump to the details row of the corresponding task by clicking on the ID in the input box to view key information such as task description and Cron expression. If users find that the ID is missing or incorrect, they can directly edit it in the input box or return to the list to reselect it to ensure the accuracy of the configured task set.

[0061] After the user confirms that the task set configuration is correct, click as follows. Figure 3 The "Start Selected Tasks" button sends a start command. After receiving the command, the operation platform executes the configured task set according to the task priority and synchronizes the execution status of each task (such as "Starting" or "Starting Successfully") to the "Status" column of the interface in real time. During the execution, a progress dialog pops up to show the overall execution progress of the batch tasks. After the execution is completed, the number of successful and failed tasks is summarized. Next to the failed tasks, the "View Failure Log" entry is displayed directly, allowing users to quickly locate problems and form a complete operation chain from start to result analysis.

[0062] Specifically, after step S08 above, which involves sending a start command to the distributed task scheduling system based on the configured task set, the method further includes: Step S0801: Receive the execution status information of the configured task set sent by the distributed task scheduling system. The execution status information includes task execution progress, task execution status identifier, and exception prompt information. Step S0802: Construct a status display area through the visualization interface, and display the execution status information according to the task ID; Step S0803: When a failed task is detected, an operation pop-up window is generated with retry options, log viewing options, and task editing options; Step S0804: Receive the target operation instruction triggered by the user based on the operation pop-up window; Step S0805: If the target operation instruction is a retry instruction, then the corresponding failed task ID is resent to the distributed task scheduling system. Step S0806: If the target operation instruction is a log viewing instruction, then obtain the task execution log returned by the distributed task scheduling system and display it through the visualization interface pop-up window; Step S0807: If the target operation instruction is a task editing instruction, then jump to the task parameter editing interface for the user to modify the task parameters.

[0063] The user client continuously receives execution status information of the configuration task set pushed by the scheduling system. This information includes task execution progress (such as the percentage of batch task completion), task execution status indicators (such as "Executing", "Success", "Failure"), and exception prompts (such as "Cron expression error" and "Executor offline"). The operation module's operation feedback area receives this status data in real time, providing a data foundation for subsequent visualization and interactive processing, and ensuring the timeliness and completeness of status information transmission.

[0064] The system leverages the scheduled task list display area of ​​the operation module to build a core area for status display. In addition to the existing columns for task ID, description, and responsible person, it adds "Execution Status" and "Progress" columns, accurately linking execution status information with task IDs. Furthermore, combined with the filtering function in the task query condition configuration area, users can quickly focus on the status of tasks they are interested in by filtering by "Status" (e.g., only viewing "Failed" tasks) or "Showing only checked options." Status indicators use different colored icons to distinguish them (e.g., green for success, red for failure), and progress is presented intuitively as a percentage progress bar, improving the readability of status information.

[0065] Meanwhile, the system monitors the task execution status in real time. Once a failed task is detected, the pop-up function in the operation feedback area of ​​the operation module is immediately triggered, generating an operation pop-up that includes retry options, log viewing options, and task editing options. Each option corresponds to a clear function guide. At the same time, the pop-up is automatically associated with the failed task ID to ensure that subsequent operations accurately point to the target task and avoid users having to manually locate failed tasks among a large number of tasks.

[0066] Then, the operation pop-up is displayed in the center of the visual interface. Users can click the corresponding option to trigger the target operation command according to their actual needs. The pop-up supports interactive optimizations such as clicking on a blank area without closing and triggering options with keyboard shortcuts, improving the convenience of operation. The system captures the user's click actions in real time, quickly responds to and receives the corresponding target operation command, and provides direction for subsequent task processing.

[0067] When the target operation command is a retry command, the system automatically extracts the failed task ID associated with the pop-up window. If there are multiple failed tasks, multiple timed tasks of the operation module can be linked to start the operation area with one click. It supports batch resending of failed task IDs to the distributed task scheduling system to initiate retry requests. During the retry process, the progress bar and status indicator in the status display area are updated in real time, and the operation feedback area displays the "Retrying" prompt in real time, allowing users to keep track of the retry progress in real time.

[0068] When the target operation command is to trigger a log viewing command, the system requests detailed execution logs of the failed task from the scheduling system. Once successfully retrieved, the logs are displayed in a pop-up window in the operation feedback area of ​​the operation module. The log pop-up window supports functions such as keyword search, log level filtering (e.g., ERROR, WARN), and log content copying, making it easy for users to quickly locate the cause of failure. At the same time, the log pop-up window retains "Close" and "Retry" buttons, allowing users to directly perform subsequent operations after viewing the logs.

[0069] When the target operation command is a task editing command, the system jumps to the task parameter editing interface. This interface reuses the simplified design concept of the task addition area in the operation module, retaining only key information input boxes such as the task scheduling frequency configuration input box, task description input box, execution parameter input box, and responsible person input box, reducing redundant editing items and lowering modification costs. The editing interface automatically loads the original parameters of failed tasks, and users can directly modify erroneous parameters based on the original parameters (such as...). Figure 4 (As shown in the example of correcting the Cron expression), after modification, clicking "Save and Re-execute" will initiate a new task execution request, forming a closed loop operation of "failure-edit-retry".

[0070] This embodiment, through the above steps, specifically involves selecting a task to be executed via a visual interface; sending the task to be executed to a distributed scheduled task system, which then loads the configuration through a configuration platform to obtain a configuration task set; receiving the configuration task set from the distributed scheduled task system; and sending a start command to the distributed scheduled task system based on the configuration task set. The distributed scheduled task system then executes the configuration task set through the operation platform based on the start command to obtain the task execution result. Thus, selecting a task to be executed directly through a visual interface eliminates the cumbersome operation of multiple page jumps. The automatic loading of task configurations and generation of configuration task sets by the configuration platform simplifies the manual configuration process. Task execution is only performed after user confirmation, lowering the learning curve. Finally, efficient task execution through the operation platform solves the problem of cumbersome operation processes and a certain learning curve in existing distributed task scheduling platforms, leading to low efficiency in actual use, thereby improving task execution efficiency.

[0071] For example, to help understand the implementation flow of the task execution method obtained by combining this embodiment with the above embodiment one, please refer to... Figure 5 , Figure 5 A simplified flowchart of a task execution method is provided, specifically: This embodiment uses the Windows task shortcut tool based on the XXL-Job management backend. The following is a complete step-by-step description of the tool's use and function implementation, covering the entire process of tool preparation, authentication, configuration, and core operations.

[0072] First, the packaging module uses the pyinstaller tool to package the Python code and related dependency libraries into an exe program that can be run directly on the Windows system. During packaging, pyinstaller automatically analyzes the dependencies, integrates the Python interpreter, Requests library, PyQt5 framework and core code, and generates an independent exe file. Users do not need to install any additional environment; they can start the tool by double-clicking the exe.

[0073] Then, the user enters their username and password in the visual interface built with PyQt5. The authentication module executes the step of "obtaining the authentication token based on the username and password", which sends a request to the XXL-Job login interface through the Requests library. After the interface verifies the token, it returns the token information. The module then executes the step of "recording the token" and saves the session information. Next, it executes the step of "returning login result information", which pops up a window to the user to provide feedback on whether the login was successful or failed.

[0074] Subsequently, the user performs the "Pass Selected Task IDs" step, selects the target task in the task list, puts the task ID into the selected task ID set, and clicks the "Configure" button. The configuration module then performs the "Read Selected Task ID Set" step and then the "Write Task ID Set to Local File" step to complete the configuration persistence, avoids repeated configuration on the next startup, and prevents accidental neglect of tasks.

[0075] Finally, perform the task addition or start / stop (it should be clear that the two operations are independent of each other): (1) Task addition process: Click the "Add" button to execute the "Display new task dialog box" step. After the user enters key parameters such as task scheduling frequency, description, and execution parameters, click confirm. The operation module executes the "Make request with new task parameters and authentication token" step. After the interface processes the request, it returns the request result and executes the "Return the addition result in the form of a pop-up window" step, providing feedback on success or failure details (such as Cron expression error message).

[0076] (2) Task start and stop process: Click the “Start Selected Task” or “Stop Selected Task” button to execute the “Read Selected Task ID Set Data” step, return the task ID set and trigger the “Secondary Confirmation Pop-up”. After the user clicks to confirm, the interface executes the “Show Progress Bar” step, the module executes the “Traverse Task ID Set” step and initiates the start and stop request, and finally executes the “Return Operation Result in Pop-up Form” step to display the start and stop status of each task and abnormal information.

[0077] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the task execution method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0078] This application also provides a task execution device, please refer to... Figure 6 The task execution device is applied to a distributed task scheduling system, which includes an operating platform and a configuration platform. The task execution device includes: The receiving module 10 is used to receive a task to be executed sent by the user terminal, wherein the task to be executed is selected by the user terminal through a visual interface; Configuration module 20 is used to load configurations for the tasks to be executed through the configuration platform to obtain a set of configuration tasks; Sending module 30 is used to send the configuration task set to the user terminal, and the user terminal sends a start command to the distributed task scheduling system based on the configuration task set; The execution module 40 is used to execute the configured task set through the operation platform based on the startup command, and obtain the task execution result.

[0079] This application also provides a task execution device, which is applied to a user terminal, and the task execution device includes: Select module 50 and choose the task to be executed through the visual interface; The sending module 60 sends the task to be executed to the distributed timed task scheduling system, which then loads the configuration through the configuration platform to obtain a set of configured tasks. Receiving module 70 receives the configuration task set sent by the distributed task scheduling system; The execution module 80 sends a start command to the distributed task scheduling system based on the configured task set. The distributed task scheduling system then executes the configured task set through the operation platform based on the start command to obtain the task execution result.

[0080] The task execution device provided in this application, employing the task execution method described in the above embodiments, can solve the technical problem that the operation process of the existing distributed task scheduling platform is cumbersome and has a certain usage threshold, resulting in low efficiency in actual use. Compared with the prior art, the beneficial effects of the task execution device provided in this application are the same as those of the task execution method provided in the above embodiments, and other technical features in the task execution device are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0081] This application provides a task execution device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the task execution method in the above embodiment 1.

[0082] The following is for reference. Figure 7 The diagram illustrates a structural schematic of a task execution device suitable for implementing embodiments of this application. The task execution device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The task execution device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0083] like Figure 7As shown, the task execution device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in the read-only memory 1002 or a program loaded from the storage device 1003 into the random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the task execution device. The processing unit 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the task execution device to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows task execution devices with various systems, it should be understood that it is not required to implement or possess all of the systems shown. More or fewer systems may be implemented alternatively.

[0084] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0085] The task execution device provided in this application, employing the task execution method described in the above embodiments, can solve the technical problem that the operation process of the existing distributed task scheduling platform is cumbersome and has a certain usage threshold, resulting in low efficiency in actual use. Compared with the prior art, the beneficial effects of the task execution device provided in this application are the same as those of the task execution method provided in the above embodiments, and other technical features of the task execution device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0086] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0087] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0088] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the task execution method described in the above embodiments.

[0089] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0090] The aforementioned computer-readable storage medium may be included in the task execution device or may exist independently and not assembled into the task execution device.

[0091] The aforementioned computer-readable storage medium carries one or more programs. When the one or more programs are executed by a task execution device, the task execution device: receives a task to be executed sent by a user terminal, the task to be executed being selected by the user terminal through a visual interface; loads the task to be executed through the configuration platform to obtain a configuration task set; sends the configuration task set to the user terminal, the user terminal sending a start command to the distributed task scheduling system based on the configuration task set; and executes the configuration task set through the operation platform based on the start command to obtain a task execution result.

[0092] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0093] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0094] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0095] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described task execution method. This solves the technical problem that existing distributed task scheduling platforms have cumbersome operation processes and certain usage barriers, resulting in low efficiency in actual use. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the task execution method provided in the above embodiments, and will not be repeated here.

[0096] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the task execution method described above.

[0097] The computer program product provided in this application can solve the technical problem that the operation process of the existing distributed task scheduling platform is cumbersome and has a certain usage threshold, resulting in low efficiency in actual use. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as the beneficial effects of the task execution method provided in the above embodiments, and will not be repeated here.

[0098] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A task execution method, characterized in that, The task execution method is applied to a distributed task scheduling system, which includes an operating platform and a configuration platform. The task execution method includes: Receive tasks to be executed sent by the user terminal, which are selected by the user terminal through a visual interface; The configuration platform is used to load the configuration of the tasks to be executed, thereby obtaining a set of configuration tasks; The configuration task set is sent to the user terminal, and the user terminal sends a start command to the distributed task scheduling system based on the configuration task set. Based on the startup command, the configured task set is executed through the operating platform to obtain the task execution result.

2. The task execution method as described in claim 1, characterized in that, Before the step of receiving the task to be executed sent by the user terminal, the method further includes: Receive login requests sent by the user client; The login request is parsed to obtain the login key, and the user parameters are loaded using the login key. Based on the user parameters, user permission information and a list of executable tasks are loaded. A visual interface is generated based on the user permission information and the list of executable tasks, allowing the user to select tasks.

3. The task execution method as described in claim 1, characterized in that, The step of configuring and loading the tasks to be executed through the configuration platform to obtain a configuration task set includes: Based on the task to be executed, the task ID of the task to be executed is determined by the operating platform; Based on the task ID, the selected task is confirmed through the configuration platform to obtain a set of selected task IDs; The set of selected task IDs is sent to the user terminal, and the user terminal sends a configuration command to the distributed task scheduling system after confirming that the set of selected task IDs is correct. According to the configuration instructions, the set of selected task IDs is written into the configuration file through the configuration platform to obtain the configuration task set.

4. The task execution method as described in claim 1, characterized in that, The step of executing the configured task set through the operating platform based on the startup command and obtaining the task execution result includes: Based on the configured task set, the operation task ID set is obtained by querying the configuration platform. The task ID set is sent to the user terminal, and the user terminal, after confirming that the task ID set is correct, sends a confirmation command to the distributed task scheduling system. Upon receiving the confirmation instruction, the task parameters are obtained by traversing the set of operation task IDs through the operation platform; The operation task ID set is executed based on the task parameters to obtain the task execution result.

5. The task execution method as described in claim 1, characterized in that, After the step of configuring and loading the task to be executed through the configuration platform to obtain a configuration task set, the method further includes: Receive the task addition instruction sent by the user terminal; Based on the task addition instruction, load the new task session box through the operation platform; The new task session box is sent to the user terminal, and the user terminal adds the new task parameters to the new task session box and then sends the new instruction to the distributed task scheduling system; The system performs a task addition determination based on the newly added task parameters and the authentication token from the user terminal. If the judgment result is successful, a success message will be sent to the user terminal through the new task dialog box.

6. A task execution method, characterized in that, The task execution method is applied to the user terminal, and the task execution method includes: Select the task to be executed through the visual interface; The tasks to be executed are sent to the distributed timed task scheduling system, which loads the configuration through the configuration platform to obtain a set of configured tasks. Receive the set of configured tasks sent by the distributed task scheduling system; Based on the configured task set, a start command is sent to the distributed task scheduling system. The distributed task scheduling system then executes the configured task set through the operating platform based on the start command, and obtains the task execution result.

7. The task execution method as described in claim 6, characterized in that, After the step of sending a start command to the distributed task scheduling system based on the configured task set, the method further includes: The system receives execution status information of the configured task set sent by the distributed task scheduling system. The execution status information includes task execution progress, task execution status identifier, and exception prompt information. The visualization interface is used to construct a status display area, which displays the execution status information according to the task ID. When a failed task is detected, a pop-up window is generated with retry options, log viewing options, and task editing options. Receive the target operation command triggered by the user based on the operation pop-up window; If the target operation instruction is a retry instruction, the corresponding failed task ID will be resent to the distributed task scheduling system. If the target operation instruction is a log viewing instruction, then the task execution log returned by the distributed task scheduling system is obtained and displayed in the visualization interface pop-up window; If the target operation command is a task editing command, the user will be redirected to the task parameter editing interface to modify the task parameters.

8. A task execution device, characterized in that, The task execution device is applied to a distributed task scheduling system, which includes an operating platform and a configuration platform. The task execution device includes: The receiving module is used to receive tasks to be executed sent by the user terminal, which are selected by the user terminal through a visual interface; The configuration module is used to load the configuration of the task to be executed through the configuration platform to obtain a configuration task set; The sending module is used to send the configuration task set to the user terminal, and the user terminal sends a start command to the distributed task scheduling system based on the configuration task set; The execution module is used to execute the configured task set through the operating platform based on the startup command, and obtain the task execution result.

9. A task execution device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the task execution method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the task execution method as described in any one of claims 1 to 7.

Images