GALANTHUS / ABI FUNCTION REFERENCE
gln_get_backend_result_outcome
Declared in <galanthus/c_api/gln_capi.h>.
GLN_API gln_backend_outcome_t GLN_CALL gln_get_backend_result_outcome(const gln_backend_result_t* in_result);
Purpose
Returns the high-level outcome stored in a backend result envelope: success, action required, follow-up required, rejected, error, or unknown.
Return
Returns the high-level outcome stored in a backend result envelope: success, action required, follow-up required, rejected, error, or unknown.
| Type | Nullability | Ownership |
|---|---|---|
gln_backend_outcome_t | value | value |
Parameters
| Name | Direction | Type | Nullability | Ownership |
|---|---|---|---|---|
in_result | input | const gln_backend_result_t* | nullable | borrowed |
Notes
Passing NULL for in_result is allowed and returns GLN_BACKEND_OUTCOME_UNKNOWN.
Outcome Semantics
GLN_BACKEND_OUTCOME_ACTION_REQUIRED means the envelope carries interrupt details and usually a continuation instead of a typed payload view. Use gln_get_backend_result_status to identify TAN, decoupled approval, or VoP confirmation.
GLN_BACKEND_OUTCOME_FOLLOW_UP_REQUIRED means the envelope carries a typed payload that the caller must consume before performing a documented explicit follow-up operation. It has status GLN_ERR_FOLLOW_UP_REQUIRED, no error or interrupt view, no continuation, and cannot be resumed with gln_resume_continuation.
GLN_BACKEND_OUTCOME_SUCCESS means the envelope kind selects the typed payload accessor. Rejected and error outcomes expose details through gln_get_backend_result_error.
See Backend Results for the envelope flow.