Vocabulary

Trigger - Initiator of a Mesa Automation. This could be a new order, fulfillment update, change in customer record, or similar changes in Shopify and external systems' record data such as Webhook, API or FTP file. A Trigger's Script governs what path its data takes to an "Action".

Log Retention - Specifies how long task details are stored. This includes the payload, context, and all logs related to the execution of this task. Tasks can be replayed as long as the log information is retained.

ComputeThe maximum time and memory limits that may be consumed during an individual run of a script. Time and compute resources related to the Trigger or Action (ie the time required to download a file from an  FTP  server) is not included.

Incoming Rate Limit - The number of incoming requests that can be made per second. This applies to JSON Webhook and Shopify Webhook Triggers and all Admin API calls. Any requests made that are over the Rate Limit will return a 429 Over Limit response.

API Key - This is the API key required to make requests to the Mesa API Layer.

Minimum Polling Interval - The most frequent interval available for a scheduled Trigger. For example every 10 minutes, every 5 minutes, or every minute.

Queue - A chronological list of actions that Mesa has taken on your behalf, including status, and supporting inspection and replays of Tasks.

Task - An individual activity. The execution of each Trigger and Action are unique tasks. For example, if you are uploading a CSV with 100 roles, there will be an Trigger Task that parses the CSV and calls an action. There will also be 100 Action Tasks each with their individual payload, logs, and status.

Replay - Allowing the re-running of any Task. Replays are helpful for debugging, testing, and fixing issues with an individual failed task. You are able to adjust the Payload before replaying the Task.

Action - Destination for a Mesa Task. This could be writing to a CSV file, synching order updates to Shopify, "batching" data updates (see Virtual Output below), or similar changes in Shopify and external systems' record data. An Actions' Script is responsible for processing Trigger data and triggering the end of the Mesa Task flow.

Virtual Output - Holding pen for Trigger data that will be processed by another Action. Most commonly used for "batching" updates in or out of Shopify. Mentioned separately because they are distinct from the other standard Actions in that they share some properties of both Triggers and Actions.

Script - Written in JavaScript (ES6 supported) code, Mesa Scripts accept a payload and can map fields, make API requests, and call Mesa SDK Methods.

Storage - Key-value storage makes it possible to create, read and modify state from within Scripts, the web interface, or REST API.

Credentials - Credentials are a type of key-value storage used to store sensitive information and are encrypted at rest. 

Connection - The authentication and communication with an external service. Contains a Trigger and/or an Action.
Step - A Trigger or an Action in an Automation.
Automation - A single workflow. Contains 1 Trigger and 1 (or more) Actions.
Task - The record of a Step that has been run/executed.

Logging - Full request information will display in the Logs tab for your automations.

Verbose Logging - Applies full debug mode, so you will see the full request information and any logs from calls to Mesa.log.debug() in the Logs tab for your automations.