Workflow & Global Activity Pages

The Activity system in Arigato provides a centralized way to monitor, debug, and analyze automation executions across your store. It helps understand what ran, when it ran, and whether it succeeded or failed, making it an essential tool for troubleshooting and performance tracking.

Overview

The Activity area is divided into two main views:

  • Workflow Activity Page – Shows execution history for a specific workflow.
  • Global Activity Page – Provides a unified view of all workflow executions across your account.

Both views help you track automation performance, inspect logs, and debug issues in real time.

Workflow Activity Page

The Workflow Activity Page focuses on a single automation workflow. Every time a workflow runs, an execution record is created and displayed in this view.

Each row in the activity table represents one execution and includes key metadata such as:

  • Status – Indicates whether the execution succeeded or failed.
  • Title – The item or object that triggered the workflow (e.g., product, order, or customer).
  • Workflow ID – The unique identifier for the workflow, hyperlinked to the actual workflow edit page.
  • Job – Background job reference (if applicable).
  • Actions – Number of actions executed within the workflow.
  • Started – Timestamp showing when the execution began.

This page is particularly useful when debugging a single automation or validating expected behavior after making changes to a workflow.

Global Activity Page

The Global Activity Page provides a broader, account-wide view of all workflow executions. Instead of focusing on a single automation, it aggregates activity across every workflow in your store.

This view is ideal for:

  • Identifying recurring failures across workflows
  • Tracking execution volume over time
  • Auditing automation activity across your store

Filters & Search

Both Activity views include advanced filtering tools to help you quickly find relevant executions.

  • Status Filter – Filter by success, failure, or all executions.
  • Workflow Filter – Narrow results to a specific workflow.
  • Object ID – Search by the Shopify object that triggered the execution.
  • Execution ID – Admin-only lookup for a specific run.
  • Date Filter – Restrict results to a specific time range.

These filters are especially useful in high-volume stores where many workflows run simultaneously.

Execution Details

Clicking on an activity row opens a detailed execution panel. This view provides deep visibility into what happened during the run.

Inside the execution details, you can access:

  • View Object – The Shopify object that triggered the workflow (e.g., product or order).
  • View Result – The output or outcome of the workflow execution.
  • View Log – Step-by-step execution logs for debugging.

Logs often include information such as condition checks, API requests, and action results (e.g., Shopify GraphQL requests, inventory updates, or tagging actions).

Understanding Statuses

Each execution displays a status indicator to help you quickly assess outcomes:

  • Success – The workflow executed without errors.
  • Failed – One or more steps encountered an error.
  • Skipped – Conditions were not met, so the workflow did not run actions.

Status indicators are especially useful when monitoring automation reliability over time.

Troubleshooting & Usage Tips

Execution ran but no actions occurred: Check condition logs to confirm whether workflow conditions evaluated to TRUE.

Shopify API request issues: Open the View Log panel to inspect GraphQL request details, including cost, throttle status, and response errors.

Missing executions: Verify the correct workflow filter is selected and ensure the correct date range is applied.

Unexpected results: Use View Result to confirm what data was passed between steps in the workflow.

Best Practices

  • Use execution logs when testing new workflows before deploying them broadly.
  • Filter by Object ID when debugging specific Shopify items.
  • Monitor API cost and throttle status in GraphQL logs for performance optimization.

The Activity system is a core part of maintaining reliable automation in Arigato, giving you full visibility into how workflows behave in production.