HotMeshGraph: {
    activities: Record<string, any>;
    expire?: number;
    hooks?: HookRules;
    input?: {
        schema: Record<string, any>;
    };
    output?: {
        schema: Record<string, any>;
    };
    persistent?: boolean;
    publishes?: string;
    subscribes: string;
    transitions?: Record<string, any>;
}

Type declaration

  • activities: Record<string, any>

    the activities that define the graph

  • Optionalexpire?: number

    the number of seconds that the completed job should be left in the store before it is deleted

  • Optionalhooks?: HookRules

    the reentrant hook rules that define how to reenter a running graph

  • Optionalinput?: {
        schema: Record<string, any>;
    }

    the schema for the input of the graph

    • schema: Record<string, any>
  • Optionaloutput?: {
        schema: Record<string, any>;
    }

    the schema for the output of the graph

    • schema: Record<string, any>
  • Optionalpersistent?: boolean

    if the graph is reentrant and has open activities, the persistent flag will emit the job completed event. This allows the 'main' thread/trigger that started the job to signal to subscribers (or the parent) that the job is 'done', while still leaving the job in a state that allows for reentry (such as cyclical hooks).

  • Optionalpublishes?: string

    the unique topic that the graph publishes/emits to when the job completes

  • subscribes: string

    the unique topic that the graph subscribes to, creating one job for each idempotent message that is received

  • Optionaltransitions?: Record<string, any>

    the transitions that define how activities are connected