Granted Patent B2

US 12,572,826 · App. 17/993,761 · Granted Mar 10, 2026

Inventors: Parth Vijay Vaishnav (San Francisco, CA); Mitchell Christensen (San Francisco, CA); Kevin Han (San Francisco, CA)

Assignee: Salesforce, Inc.

G06N5/025G06F9/4881

Abstract

Claims (46)

1 . A computing device, comprising:

one or more processors; and

a non-transitory machine-readable storage medium that provides instructions that, if executed by the one or more processors, are configurable to cause the computing device to compile rules for a rules engine by:

receiving, by an event handler, a compile rules event from a process external to a rule compiler;

retrieving a set of rules from a database;

loading the set of rules into a memory, wherein the set of rules includes template rules and non-template rules;

fetching data from a data source, wherein placeholder variables included in the template rules are replaced with the fetched data;

generating a rules language specification based on the template rules and the non-template rules;

executing a compilation thread on the rules language specification to generate compiled rules;

asynchronously executing an execution thread concurrently with the compilation thread to perform a rule execution process;

storing a serialized knowledge base in a database for use by the rules engine during a subsequent rule execution process, wherein the serialized knowledge base includes serialized compiled rules; and

outputting a compile completion event.

2 . The computing device of claim 1 , wherein the compilation thread is on a tier lower than the execution thread.

3 . The computing device of claim 1 , wherein the compilation thread is executed in a multi-tenant infrastructure servicing multiple organizations, and wherein concurrency of compilation thread execution is set to one per organization so that only one compilation thread runs is executed at a time per organization.

4 . The computing device of claim 1 , further comprising a retry mechanism, which responsive to a non-blocking recoverable error, a rule compilation process is re-enqueued after a period of time to provide infrastructure time to recover.

5 . The computing device of claim 1 , further comprising a failure handling mechanism, which responsive to a non-recoverable failure, stops a compilation process and sends a failure event to a user explaining the failure.

6 . The computing device of claim 1 , further comprising configuration guardrails to prevent excessive resource utilization, the configuration guardrails including maximum limits on a number of rules per rule set, a number of template rules per rule set, and an overall size of a compiled knowledge base.

7 . A non-transitory machine-readable storage medium that provides instructions that, if executed by a set of one or more processors, are configurable to cause the set of one or more processors to perform operations comprising:

receive, by an event handler, a compile rules event from a process external to a rule compiler;

retrieve a set of rules from a database; load the set of rules into a memory, wherein the set of rules includes template rules and non-template rules;

fetch data from a data source, wherein placeholder variables included in the template rules are replaced with the fetched data;

generate a rules language specification based on the template rules and the non-template rules;

execute a compilation thread on the rules language specification to generate compiled rules;

asynchronously execute an execution thread concurrently with the compilation thread to perform a rule execution process;

store a serialized knowledge base in a database for use by a rules engine during a subsequent rule execution process, wherein the serialized knowledge base includes serialized compiled rules; and

output a compile completion event.

8 . The non-transitory machine-readable storage medium of claim 7 , wherein the compilation thread is on a tier lower than the execution thread.

9 . The non-transitory machine-readable storage medium of claim 7 , wherein the compilation thread is executed in a multi-tenant infrastructure servicing multiple organizations, and wherein concurrency of compilation thread execution is set to one per organization so that only one compilation thread is executed at a time per organization.

10 . The non-transitory machine-readable storage medium of claim 7 , further comprising a retry mechanism, which responsive to a non-blocking recoverable error, a rule compilation process is re-enqueued after a period of time to provide infrastructure time to recover.

11 . The non-transitory machine-readable storage medium of claim 7 , further comprising a failure handling mechanism, which responsive to a non-recoverable failure, stops a compilation process and sends a failure event to a user explaining the failure.

12 . The non-transitory machine-readable storage medium of claim 7 , further comprising configuration guardrails to prevent excessive resource utilization, the configuration guardrails including maximum limits on a number of rules per rule set, a number of template rules per rule set, and an overall size of a compiled knowledge base.

13 . A method comprising:

receiving, by an event handler, a compile rules event from a process external to a rule compiler;

retrieving a set of rules from a database;

loading the set of rules into a memory, wherein the set of rules includes template rules and non-template rules;

fetching data from a data source, wherein placeholder variables included in the template rules are replaced with the fetched data;

generating a rules language specification based on the template rules and the non- template rules;

executing a compilation thread on the rules language specification to generate compiled rules;

asynchronously executing an execution thread concurrently with the compilation thread to perform a rule execution process;

storing a serialized knowledge base in a database for use by a rules engine during a subsequent rule execution process, wherein the serialized knowledge base includes serialized compiled rules; and

outputting a compile completion event.

14 . The method of claim 13 , wherein the compilation thread is on a tier lower than the execution thread.

15 . The method of claim 13 , wherein the compilation thread is executed in a multi-tenant infrastructure servicing multiple organizations, and wherein concurrency of compilation thread execution is set to one per organization so that only one compilation thread is executed at a time per organization.

16 . The method of claim 13 , further comprising a retry mechanism, which responsive to a non-blocking recoverable error, a rule compilation process is re-enqueued after a period of time to provide infrastructure time to recover.

17 . The method of claim 13 , further comprising a failure handling mechanism, which responsive to a non-recoverable failure, stops a compilation process and sends a failure event to a user explaining the failure.

18 . The method of claim 13 , further comprising configuration guardrails to prevent excessive resource utilization, the configuration guardrails including maximum limits on a number of rules per rule set, a number of template rules per rule set, and an overall size of a compiled knowledge base.

Assignments (1)

Continuity (1)

References Cited (230)