Product — Automation
Workflows that survive the real world.
Durable processes that trigger, decide, execute and verify — and recover when a step fails, rather than starting over.
- Trigger
- Decide
- Execute
- Verify
- Recover
The processes rules could not reach
Most of what remains un-automated in an organisation was left behind for the same reason: it required judgement. Not "if this then that", but reading a document, weighing an exception, deciding whether something is close enough. That is the work this is for.
Triggers
Schedules, events, inbound messages, system webhooks, or a person asking. The entry point is not the interesting part — what happens next is.
Durability
State is checkpointed at every step. A crashed process resumes from its last good point instead of replaying side effects.
Recovery
Failures are classified: retry, escalate, or compensate. A workflow that only knows how to fail is not automation, it is a pager.
Idempotency by default
Anything that can run twice eventually will. Actions carry idempotency keys so a retried step does not send a second email, create a second record or make a second payment. This is unglamorous and it is the difference between automation you can leave running and automation you have to watch.
Reversibility
Irreversible actions are identified as such and treated differently: they require explicit authorisation, and they are the last thing a workflow does rather than the first. Where a compensating action exists, it is defined alongside the action it undoes.
Worth knowing
Not everything should be automated. Work with low volume and high consequence is usually better served by a good interface than by an unattended process.
Automation makes existing process problems faster. It does not fix them.
Build what comes next.
Tell us what you are trying to build. We will show you how ORYN would approach it.