Triggering Runners #

This doc explains how runners can be triggered to process something right now instead of waiting for the background process to pick it up.

API Endpoints #

Triggering all the runners #

Running the fetch command below will run all the runners one by one.

fetch("/api/tick/runners", { method: "POST" });

Note: If a runner is already running in the background it will respond with 500 status code

Triggering individual runner #

Running the fetch command below will run the specified runner

fetch("/api/internal/runner/{runner_id}/run", {
  method: "POST",
  body: JSON.stringify({
    options: {
      messages_to_process: 100,
    },
  }),
});

Passing options in the body is optional, it can be skipped and an empty body can be passed as by default it processes 100 messages.

Runner ID can be one of the following:

• calendar_events - Checks calendar events (mainly for meeting summaries)
• chat_summary_notes - Creates note summary from slack messages
• conversation_note_analysis_processor - Analyses conversation / notes for labels (action_items, task_issue_bug…)
• needle_mover - Processes the needle mover conversations / notes
• needle_mover_scheduler - Looks for conversations and notes to be processed for needle mover
• scheduled_meetings - Creates the meeting summary
• slack_message_delivery - Sends the meeting summary over slack