WEBVTT

00:00:01.000 --> 00:00:04.935
A workflow is useful only when someone understands what to do

00:00:04.960 --> 00:00:06.570
when it fails.

00:00:06.600 --> 00:00:09.930
A fictional training company receives a registration.

00:00:09.960 --> 00:00:13.930
Its workflow checks the fields, creates a contact and prepares a

00:00:14.240 --> 00:00:15.210
confirmation.

00:00:15.240 --> 00:00:18.850
Then the connection to the customer system becomes unavailable.

00:00:19.240 --> 00:00:23.690
Define the information each stage receives and what confirms success.

00:00:24.360 --> 00:00:28.730
A received registration, a confirmed contact and a sent message are

00:00:28.840 --> 00:00:30.970
different events, with different evidence.

00:00:31.480 --> 00:00:35.050
Keep a recognisable reference for the same registration.

00:00:35.400 --> 00:00:38.810
Before repeating a step, check what has already happened.

00:00:39.000 --> 00:00:43.850
Otherwise a temporary failure can produce another contact or a duplicate message.

00:00:44.680 --> 00:00:48.490
No response from the customer system does not necessarily mean nothing

00:00:48.520 --> 00:00:49.450
was saved.

00:00:49.640 --> 00:00:52.210
Investigate the destination first.

00:00:52.600 --> 00:00:57.250
Give an unknown outcome a visible status rather than assuming it failed.

00:00:57.480 --> 00:01:01.450
An administrator needs to see the failed stage, the relevant input

00:01:01.640 --> 00:01:03.370
and the permitted recovery action.

00:01:04.120 --> 00:01:09.730
Keep access restricted; credentials should not appear as plain text in the workflow.

00:01:10.120 --> 00:01:14.170
Test a repeated registration, missing fields and a failure after

00:01:14.280 --> 00:01:14.810
saving.

00:01:15.320 --> 00:01:19.930
Then check both systems: recovery should leave one correct outcome,

00:01:20.000 --> 00:01:22.810
while unresolved work remains visible to its owner.

00:01:23.640 --> 00:01:26.290
Develop one bounded workflow first.

00:01:26.520 --> 00:01:30.250
Have its future administrator locate a failed run and follow the

00:01:30.320 --> 00:01:33.690
agreed recovery process before connecting more stages.

00:01:34.520 --> 00:01:39.610
Read OXIAE’s n8n consulting guide for the connection between process

00:01:39.640 --> 00:01:42.330
design, exceptions and maintenance.