Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.digifist.com/llms.txt

Use this file to discover all available pages before exploring further.

Every automation execution in Galantis is recorded in the AutomationActivity log. Each time a customer passes through a node — whether it completes successfully, is skipped, fails, or is still pending — a record is written with the outcome and a timestamp. This gives you a complete, per-customer audit trail for every flow without any manual tracking.

​
What this covers

  • The activity log and what it records
  • Node execution statuses and what each means
  • How to use the activity log for troubleshooting
  • What skipped executions indicate

​
What is recorded

For every customer enrolled in an automation, Galantis records:
  • The automation and the specific flow version they were enrolled in
  • Each node they passed through, in sequence
  • The status of each node execution
  • Timestamps for each status transition
  • The reason for any skip or failure
This data is stored in AutomationActivity and is accessible in Automations → [Automation Name] → Activity.

​
Node execution statuses

StatusMeaning
PENDINGThe node is queued — execution has not yet started for this customer at this node
SCHEDULEDA Delay Node is active — execution is paused and will resume after the delay elapses
COMPLETEDThe node executed successfully — a message was sent, a condition was evaluated, or a delay elapsed
FAILEDExecution failed — the action could not be completed, typically due to an API error or template issue
SKIPPEDExecution was bypassed — see below for skip reasons

​
Understanding SKIPPED

SKIPPED is not an error. It indicates that Galantis deliberately did not execute the node for a valid reason. Common skip reasons:
  • Consent — The customer’s marketing_state changed to UNSUBSCRIBED or REDACTED between enrollment and reaching this node. Sending the message would violate WhatsApp’s policy.
  • Frequency cap — The customer was already enrolled in this automation within the configured cap window. The trigger was detected but enrollment was suppressed.
  • Exclusion rule — The customer became a member of an excluded list or segment before reaching this node.
  • Condition branch — The customer took the YES branch of a Condition Node, so the NO branch nodes were skipped, and vice versa. This is normal flow behavior.
Reviewing skipped executions is particularly useful for diagnosing why a specific customer did not receive an expected message — the skip record shows exactly which check caused the bypass.

​
Using the activity log

1

Open the activity log

Go to Automations → [Automation Name] → Activity.
2

Find the customer

Search or filter by customer name, phone number, or email to find a specific customer’s execution record.
3

Review the node sequence

The activity log shows each node the customer passed through in order, with its status and timestamp. Trace the path from enrollment through each node to see where execution completed, stalled, or was skipped.
4

Expand a node record

Click a node record to see its full detail — the specific status reason, the template used (for Action Nodes), and any error message for FAILED statuses.

​
Common troubleshooting scenarios

Customer enrolled but never received a message Check whether any Action Nodes in their execution path show SKIPPED. If yes, expand the skip record to see the reason — consent change, frequency cap, or exclusion rule. If all Action Nodes show COMPLETED, the message was dispatched — check the message delivery status in Audience → Contacts → [Customer] → Messages for the delivery outcome. Customer shows SCHEDULED with no further activity The customer is currently inside a Delay Node. SCHEDULED means the delay is still running — execution will continue automatically when the delay elapses. This is not a stuck state unless the timestamp is significantly older than the configured delay duration. Action Node shows FAILED Expand the failure record to see the error reason. Common causes:
  • Template was paused by Meta after the automation was activated — resolve the template issue and re-activate
  • Customer’s phone number has a format error — review the contact record for a missing country calling code
  • Insufficient credits — check billing balance
Customer was not enrolled at all The customer’s trigger event fired but they were not enrolled. Check the activity log for a blocked enrollment record. Possible reasons: consent was not SUBSCRIBED at trigger time, frequency cap was active, or the customer was a member of an excluded list or segment.
  • Flow Builder — Understanding the node structure that activity tracking maps to
  • Frequency Caps — How cap-blocked enrollments appear in the activity log
  • Exclusion Rules — How exclusion-blocked enrollments appear in the activity log
  • Opt-in & Consent — Consent states that cause SKIPPED execution