Automated generation of workflows
US-2019205792-A1 · Jul 4, 2019 · US
US11086671B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11086671-B2 |
| Application number | US-202017065843-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 8, 2020 |
| Priority date | Feb 5, 2016 |
| Publication date | Aug 10, 2021 |
| Grant date | Aug 10, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An apparatus includes processor(s) to: receive, a request to cancel a performance of a job flow; store, within a task kill queue, a kill tasks request message; within a task container, in response to the storage of the kill tasks request message, cease execution of instructions of a task routine to cease performance of a task of a set of tasks of the job flow, and store, within a task queue, a task cancelation message indicating cancelation of execution of the task routine; within a performance container, execute instructions of a performance routine to cause the at least one processor to, in response to the storage of the task canceled message, store, within a job queue, a job cancelation message indicating cancelation of the job flow; and in response to the storage of the job cancelation message, transmit an indication of cancelation of the job flow to the requesting device.
Opening claim text (preview).
The invention claimed is: 1. An apparatus comprising at least one processor and a storage to store instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising: receive, at the at least one processor and from a requesting device via a network, a request to cancel a performance of a job flow, wherein: the job flow is defined in a job flow definition that specifies a set of tasks to be performed via execution of a corresponding set of task routines during the job flow performance; the job flow definition is stored among multiple job flow definitions within at least one federated area; the set of task routines is stored among multiple task routines within the at least one federated area; and the at least one federated area is maintained within at least one storage device; store, within a task kill queue, a kill tasks request message comprising a job flow identifier of the job flow; within a first task container, in response to the storage of the kill tasks request message within the task kill queue, perform operations comprising: cease execution of instructions of a first task routine of the set of task routines to cease performance of a first task of the set of tasks of the job flow; and store, within a task queue, a first task cancelation message indicative of cancelation of execution of the first task routine; within a second task container, in response to the storage of the kill tasks request message within the task kill queue, perform operations comprising: cease execution of instructions of a second task routine of the set of task routines to cease performance a second task of the set of tasks of the job flow; and store, within the task queue, a second task cancelation message indicative of cancelation of execution of the second task routine; within a first performance container, execute instructions of a first instance of a performance routine to cause the at least one processor to, in response to the storage of either the first task canceled message within the task queue or the second task canceled message within the task queue, perform operations comprising: store, within a job queue, a job cancelation message indicative of cancelation of the job flow; and in response to the storage of the job cancelation message within the job queue, transmit an indication of cancelation of the job flow to the requesting device via the network. 2. The apparatus of claim 1 , wherein: within the first performance container, a first task routine execution request message and a second task routine execution request message were stored within the task queue and the task queue was monitored for indications of completion of execution of the set of task routines in response to storage, within the job queue, of a job performance request message comprising the job flow definition of the job flow; within the first task container, execution of the instructions of the first task routine commenced within the first task container in response to the storage of the first task routine execution request message within the task queue; within the second task container, execution of the instructions of the second task routine commenced within the second task container in response to the storage of the second task routine execution request message within the task queue; and the at least one processor is caused to, within the first performance container, in response to the storage of either the first task canceled message within the task queue or the second task canceled message within the task queue, perform operations comprising: cease monitoring of the task queue for indications of completion of execution of the set of task routines. 3. The apparatus of claim 1 , wherein the at least one processor is caused to perform operations comprising: within a first portal container, execute instructions of a first instance of a portal routine to cause the at least one processor to, in response to receiving the request to cancel the performance of the job flow from the requesting device, perform operations comprising: in preparation for uninstantiation of the first portal container, store, within a job kill queue, a kill job request message comprising the job flow identifier of the job flow; and in response to the storage of the kill job request message within the job kill queue: generate the kill tasks request message; store the kill tasks request message within the task kill queue; monitor the job queue for the job cancelation message; and in response to storage of the job cancelation message within the job queue, transmit the indication of cancelation of the job flow to the requesting device via the network. 4. The apparatus of claim 1 , wherein the at least one processor is caused to perform operations comprising: within a first portal container, execute instructions of a first instance of a portal routine to cause the at least one processor to, in response to receiving the request to cancel the performance of the job flow from the requesting device, perform operations comprising: in preparation for uninstantiation of the first portal container, store, within a job kill queue, a kill job request message comprising the job flow identifier of the job flow; and in response to the storage of the kill job request message within the job kill queue, generate the kill tasks request message; within a second portal container, execute instructions of a second instance of the portal routine to cause the at least one processor to, in response to the storage of the kill job request message within the job kill queue and in response to the uninstantiation of the first portal container, perform operations to take over for the first portal container that comprise: generate the kill tasks request message; store the kill tasks request message within the task kill queue; monitor the job queue for the job cancelation message; and in response to storage of the job cancelation message within the job queue, transmit the indication of cancelation of the job flow to the requesting device via the network. 5. The apparatus of claim 1 , wherein the at least one processor is caused to perform operations comprising: receive, via the network, a request to perform the job flow; retrieve the job flow definition from among the multiple job flow definitions in the at least one federated area; store, within the job queue, a job performance request message comprising the job flow definition; within the first performance container, in response to the storage of the job performance request message within the job queue, perform operations comprising: derive an order of performance of the set of tasks that specifies at least the first task of the set of tasks to be performed, and that is based on indications in the job flow definition of dependencies among the set of tasks; store, within the task queue, a first task routine execution request message comprising an identifier associated with the first task; and monitor the task queue for an indication of completion of execution of the first task routine; and within the first task container, in response to the storage of the first task routine execution request message within the task queue, perform operations comprising: use the identifier associated with the first task to retrieve the first task routine from the at least one federated area; and commence execution, within the first task container, of instructions of the first task routine to commence performance of the first task. 6. The apparatus of claim 5 , wherein: the request to perform a job flow comprises the job flow identifier of the job flow definition; the retrieval of the job flow definition comprises use of the job flow ident
Combinations of networks · CPC title
Recurrent networks, e.g. Hopfield networks · CPC title
Learning methods · CPC title
Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34) · CPC title
Message passing systems or structures, e.g. queues · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.