Who this is for
An operations manager or small-business owner who runs a process from an Airtable base and whose automation shows failed runs or does not fire for some records.
Notification emails stopped, a status change did nothing, or the automation history shows failed runs that nobody looked at.
The result
With synthetic records for three agreed cases, one named automation either runs successfully or skips as the note documents, history shows Ran successfully for the cases meant to run, and a deliberately failing case produces an alert to the named person.
What is included
- One automation in one base, with its trigger and up to five actions read in full
- Diagnosis from the automation history of why runs fail or records are skipped
- Repair on the trigger conditions, an action input, or one short script, and add an 'is not empty' condition on inputs where that is the cause
- Test three agreed cases on test records, and one failing case to prove the alert reaches the named person
- A maximum number of test runs, written into the quote at scoping and set from the three cases, the failing case and any rerun you accept, then checked against what is left of your workspace's monthly run allowance
You receive
- A short note naming the cause, with the relevant history entries redacted
- The repaired automation, with change notes and how to reverse them
- A test log: the three cases, expected behaviour, history status and run count used
- A list of conditions under which the automation will legitimately not run, in plain words
What is not included
- Raising your plan's automation run limits or per-base automation limits, or reconnecting third-party accounts, which the account holder does
- More than one automation, or rebuilding the base or its views
- Restructuring tables or fields, which is a separate job
- Scripts beyond one short script action
- Real customer records or any message sent to a real recipient during testing
What we need from you first
- The base and automation names, the trigger type and the action that fails, with its redacted error text
- Whether the failing record has an empty linked field, an attachment or a large table behind it
- Who last switched the automation on
- Do not send record exports, passwords or a base invitation in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- For each of the three agreed test cases, the automation either shows Ran successfully in its history with the intended effect, or is documented in the note as deliberately not running for that case.
- A deliberately failing case produces a failure notification to the named person, and that person is recorded as a collaborator with Creator permission or higher who is subscribed to it.
- The number of runs used by the tests is recorded and does not exceed the maximum number of test runs written into the quote at scoping.
- The change notes list each altered setting with its earlier value and name every condition under which the automation will not run.
You inspect the history, the received alert and the change notes, then sign off before payment. You apply the repair to the live base and check one genuine record.
When we would stop or decline
- The automation stopped because a connected account's authorisation changed and only the account holder can reconnect it
- The workspace has used its monthly automation run allowance, or has too little left for the agreed maximum number of test runs
- The person to be told cannot be given Creator permission or higher on the base
- The cause is a formula primary field or a synced table that you do not want changed
Questions
Why did the automation not run for records that already matched?
Airtable documents that records already meeting the conditions when an automation is switched on do not trigger it until they satisfy the conditions again. The note will say whether that applies.
Who gets told when it fails?
Airtable sends the failure notice to the last person who turned the automation on, and to workspace owners if that person has left. We add a named person to the alert as part of the job; Airtable only accepts a collaborator with Creator permission or higher on the base as a subscriber.
Will testing cost me runs?
Yes, a few. Airtable counts failed and successful runs. We agree a maximum number of test runs with you in writing before testing, keep to the agreed cases and report the number used.
Price and terms
£135 · untested offer price. £135 after the agreed checks pass and you sign off. No payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.