Skip to main content
Every time an automation fires, Digital Florists logs it. You can review these logs to confirm automations are working, investigate failures, and understand exactly what happened.

​
Viewing logs

Go to Settings > Automations. Each automation in the list has a Logs action — click it to see every time that automation has fired. Each log entry shows:
DetailWhat it tells you
Date and timeWhen the automation fired
RecordWhich order or event triggered it
StatusWhether the action succeeded or failed
Error detailsIf it failed, what went wrong

​
Why an automation might not fire

If an automation doesn’t seem to be working, check these common causes:

​
The automation is disabled

The most common reason. Go to Settings > Automations and check that the automation is toggled on.

​
Conditions aren’t being met

If you’ve added conditions, they all need to be true for the automation to run. For example, if your condition is “Fulfilment method equals Delivery” but the order is a collection, the automation won’t fire.
Temporarily remove your conditions to test whether the trigger itself is working. If the automation fires without conditions, you know the issue is with your condition setup.

​
The trigger doesn’t match the change

Make sure you’ve chosen the right trigger for what you’re trying to catch:
  • Created fires once, when the record is first made
  • Status changed fires when the order/event status changes (New → Confirmed, etc.)
  • Payment status changed fires when the payment status changes (Unpaid → Paid, etc.)
A common mistake is using “Status changed” when you mean “Payment status changed”, or vice versa.

​
The record was created before the automation

Automations only apply going forward. If you create an automation today, it won’t fire for orders or events that already exist — only for new triggers from this point on.

​
Email or SMS delivery issues

The automation may fire successfully (you’ll see it in the logs) but the email or SMS doesn’t arrive. This is usually:
  • The customer’s email address is incorrect or missing
  • The email went to their spam folder
  • Your SMS integration isn’t connected or has run out of credit
  • The customer’s phone number is missing from the order
Check the log entry — if the status shows success, the automation worked but the delivery channel may have an issue.

​
Common questions

Logs are kept indefinitely. You can scroll back through the full history of any automation.
There’s no replay button. If an automation failed, fix the underlying issue (e.g. a missing email address) and either wait for the next trigger or manually perform the action.
No. Automations run independently of your orders and events. A failed automation doesn’t change the order status, block payments, or affect anything else.
Automation failures are logged but don’t send notifications by default. Check your automation logs periodically, especially after setting up new automations.

​
What’s next?

Automations Overview

Back to the main automations guide.

Triggers & Conditions

Review your trigger and condition setup.

Actions

Check your action configuration.

Notifications

Manage email templates used by automations.
Last modified on March 9, 2026