Responding to action results

Action runs are performed asynchronously, like all Mechanic runs. This means their results aren't available to the Liquid task code that defined them.

To respond to action results, add a task subscription to the mechanic/actions/perform event topic. When a task includes this subscription, Mechanic will generate an event with that topic for every action that the task completes. This event will only ever be responded to by the task that generated it; it will never be sent to other tasks.

Common use cases:

• Evaluating HTTP response codes or payloads

  • See Working with external APIs

• Evaluating the results of Shopify GraphQL mutations

• Using content from generated Files

The Echo action does not generate mechanic/actions/perform events.

Inspecting the context

Events with the topic mechanic/actions/perform are, by nature, always child events. As such, their event variable contains a reference to the event's parent. This means a task may use event.parent.data to access all the data that informed the construction of the action in question. (Note that only the previous 5 generations of parents are available.)

A mechanic/actions/perform event also provides task runs with an action variable (containing the same information available in event.data). This variable contains the original action object (including its type, options, and meta information), and data from the run in which the action was performed.

Common sources of information for followup task runs:

• action.options — the original options defined for the action

• action.run.ok — true or false, indicating the action's success

• action.run.result — the value (if any) generated by the action run

• action.run.error — the error (if any) raised during the action run

• action.meta — the meta information given in the action's definition

It's important to specifically account for the mechanic/actions/perform topic when writing a task script, minding the fact that improper composition could result in an infinite loop.

Mechanic will step in and forcibly fail subsequent task runs that contain results identical to their predecessors.

Example

This example cycles between three different modes of operation, depending on the meta information recorded in the action definition. And, by checking on action.run.ok at the very beginning, the task is also able to "break" into failure-handling mode, in which an email is sent to an administrator.

Subscriptions

mechanic/user/trigger
mechanic/actions/perform

Code

{% if action.run.ok == false %}
  {% action "email" %}
    {
      "to": "[e-mail]",
      "subject": "Action failure",
      "body": {{ "Alert!<br><br>" | append: action.run.error | json }}
    }
  {% endaction %}
{% elsif event.topic contains "trigger" %}
  {% action %}
    {
      "type": "cache",
      "options": ["set", "foo", "bar"],
      "meta": {
        "mode": "first"
      }
    }
  {% endaction %}
{% elsif action.meta.mode == "first" %}
  {% capture mutation %}
    mutation {
      tagsAdd(id: "gid://shopify/Customer/1234567890", tags: ["processed"]) {
        userErrors { field, message }
      }
    }
  {% endcapture %}

  {% action %}
    {
      "type": "shopify",
      "options": {{ mutation | json }},
      "meta": {
        "mode": "second"
      }
    }
  {% endaction %}
{% elsif action.meta.mode == "second" %}
  {% action "echo", "done" %}
{% endif %}