---
title: Fallback Strategy
description: How to retrieve process results when the webhook service is temporarily unavailable.
canonical: https://developer.unico.io/human-token/webhooks-and-events/fallback
locale: en
generated_by: markdown-export
---

- [/](/)
- Additional Resources
- [Webhooks and Events](/human-token/webhooks-and-events/)
- Fallback Strategy

**On this page# Fallback Strategy

In case of any unavailability in the webhook service, it is recommended to implement a fallback mechanism to ensure your application can still retrieve the process result within the expected response time.
### How it works​

The webhook is the primary result delivery mechanism. However, you should treat the following signals as additional triggers to actively fetch the result via `GET /client/v1/process/{processId}`:
SignalChannelWhat it provides`callbackUri` redirectHuman Token Journey (`humantoken`)URL redirect only — no result
warning`callbackUri` does not deliver the process result directly. It is an end-of-journey signal only. Your back-end is responsible for correlating the redirect with the `processId` previously stored, and then calling GetProcess to retrieve the actual outcome.
### Recommended flow​

Once an end-of-journey signal is received, your back-end should call `GET /client/v1/process/{processId}` and validate the result in the following order:

Confirm `state = PROCESS_STATE_FINISHED`
Evaluate the `result` field and apply your business rules

This ensures that temporary webhook unavailability does not result in loss of process outcomes.Last updated on Oct 16, 2026**