How long is history kept?

Runs stay in History while the workflow exists. Deleting a workflow removes it from the list, together with its history.

Can I run a failed run again?

No. Fix the cause and wait for the next trigger. Workflows with the Manual trigger can be started again with Run.

Check workflow runs and failures

Every time a workflow starts, Softalon saves the run. History shows each run with its status and the result of every step, so you can see whether a message went out and why not.

Before you start

You need the Super Administrator or Owner role.

1
Step 1 of 2
Open History
Go to Workflows. On the workflow's card, open the menu and click History.
You will see:
A list of runs, newest first. Each run shows its status, the number of steps it went through and when it started.
2
Step 2 of 2
Open a run
Click a run to expand it. You see each step in order, with the time it ran and a short result, for example Notification sent successfully. or Notification not sent: no recipient specified.

Run statuses

Status	What it means
Running	The run is in progress or paused on a Wait/Delay step.
Completed	The run reached End Workflow.
Failed	A step hit an error and the run stopped.
Canceled	The run was stopped because the workflow was changed, turned off or deleted.

Completed means the run finished, not that every message was delivered. A Send Notification step that skips a message still lets the run continue. Expand the run to check each step.

Common step results

Result	What to do
Notification not sent: no recipient specified.	The recipient variable was empty, for example the client has no email address or phone number.
Notification not sent: no content specified.	Add text to the step's Content.
Notification not sent: no WhatsApp template specified.	Pick a Template in the step.
Notification not sent: client has not given transactional SMS consent.	The client hasn't agreed to transactional messages. See Client consent explained.
Notification not sent: recipient already notified via ...	The person already got a message on the same address earlier in this run. This is expected for fallbacks.
Notification not sent: INSUFFICIENT_CREDITS.	Your salon is out of credits. See Buy more credits.
HTTP request not sent: rate limit exceeded.	Your workflows sent too many requests in a short time. See Send data to another system.
Workflow execution cancelled due to workflow update.	The workflow's steps were saved while this run was in progress.
Workflow execution canceled: workflow was disabled.	The workflow was turned off while this run was waiting.

When a workflow doesn't run at all

If a run is missing from History, the workflow didn't start. Check that:

the workflow's switch is on,
your salon's subscription is active,
the trigger matches what happened. For example, Upcoming (24h) doesn't fire for an appointment booked less than 24 hours ahead. See Workflow triggers explained.

To see the messages themselves, go to your notification history. See See which notifications were sent.

Common questions

A failed step currently shows only its name. The run's Failed status tells you which step stopped it: it's the last one listed.

Related guides

How workflows workLearn how workflows automate your salon: triggers, steps, runs, the active switch and how many workflows each plan can run.

The Send Notification step explainedEvery setting of the Send Notification step: channel, recipient, subject and content, WhatsApp templates, CC and BCC, and when a message is skipped.

See which notifications were sentCheck every email, text, WhatsApp message and push notification your salon sent, for the whole salon, one team member or one client.