Creating RunTemplates¶

Target Audience: Users, Administrators Difficulty: Beginner Prerequisites: Installing Applications; understanding of Data Model

Overview ¶

A RunTemplate ties an Application to a Company and answers the questions: how should the application run, when, and with what parameters? Each RunTemplate produces one job per scheduled run.

Creating a RunTemplate via the Web Interface ¶

Open the company detail page (Companies → select company)
Click the application you want to schedule
Click “⚙️ Create RunTemplate” (or “New RunTemplate”)

Fill in the form:

Field	Required	Description
Name	Yes	Descriptive label (e.g. “Daily bank import”)
Description	No	Free-text note for documentation
Schedule / Interval	Yes	How often to run (see intervals below)
Executor	Yes	Where to run: Native, Docker, Podman, Kubernetes, Azure
Status	Yes	Active (scheduled) or Inactive (paused)
Delay	No	Seconds to delay execution after the scheduled time

Fill in any application-specific configuration fields shown below the main form
Click “Save”

Schedule Intervals ¶

Interval	Description
`Manually`	Never auto-scheduled; only run on demand
`Hourly`	Once per hour, at the top of the hour
`Daily`	Once per day
`Weekly`	Once per week
`Monthly`	Once per month
`Yearly`	Once per year

Choosing an Executor ¶

The executor determines where the job process runs:

Native — directly on the server (default; simplest)
Docker — inside a Docker container (requires ociimage in the app definition)
Podman — inside a rootless Podman container
Kubernetes — as a one-shot pod in a Kubernetes cluster
Azure — in Azure Container Instances (experimental)

See Executors for setup requirements.

Creating a RunTemplate via CLI ¶

multiflexi-cli runtemplate create \
  --company=ACME \
  --app=multiflexi-probe \
  --name="Hourly health check" \
  --interval=hourly \
  --executor=Native \
  --active=1

Listing RunTemplates ¶

# All RunTemplates
multiflexi-cli runtemplate list

# For a specific company
multiflexi-cli runtemplate list --company=ACME

Updating a RunTemplate ¶

# Pause scheduling
multiflexi-cli runtemplate update --id=42 --active=0

# Change interval
multiflexi-cli runtemplate update --id=42 --interval=daily

# Change executor
multiflexi-cli runtemplate update --id=42 --executor=Docker

Running a RunTemplate Immediately ¶

To trigger a one-off execution outside the normal schedule:

Via the web interface: Open the RunTemplate detail page → click “▶️ Execute Now”

Via CLI:

multiflexi-cli runtemplate run --id=42

Configuring Post-Job Actions ¶

Actions fire after a job completes. They can send notifications, trigger further jobs, or post data to external systems.

Open the RunTemplate detail page
Click “Actions” tab
Click “+ Add Action”
Select the action type and configure it
Set the trigger condition: on success, on failure, or always

See Actions for all available actions.

Deleting a RunTemplate ¶

Warning

Deleting a RunTemplate does not delete existing job history. Use Inactive status to pause without deleting.

multiflexi-cli runtemplate delete --id=42