Resolve a stuck return-file transmission
Applies one human remedy to a submission no automatic path can finish. probe_now asks Lerian STA whether a transfer for this file already exists and binds it if so; attach_transfer binds a transfer you located, but ONLY after Lerian STA confirms it belongs to this file; force_fail gives up on a stuck submission so the file becomes reconsolidable; cancel_now retries cancelling a size-mismatched transfer that is still live at Lerian STA. reason is required and MUST NOT contain personal data or monetary values — it is written verbatim into the audit trail. 422 names the door that IS open when the action does not apply to the file’s state.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
The return file id (UUID).
"dddddddd-dddd-dddd-dddd-dddddddddddd"
Body
probe_now asks Lerian STA whether a transfer for this file already exists; attach_transfer binds one you located, after Lerian STA confirms it is this file's; force_fail gives up on a stuck submission so the file becomes reconsolidable; cancel_now retries cancelling a size-mismatched transfer that is still live.
probe_now, attach_transfer, force_fail, cancel_now "probe_now"
The institution the return file belongs to (UUID).
"44444444-4444-4444-4444-444444444444"
Why this remedy is being applied, in your own words. MUST NOT contain personal data (CPF/CNPJ, names, process numbers) or monetary values: it is written verbatim into a permanent, append-only audit record. Text carrying a run of more than 10 digits is refused with 422 — that is a floor against pasting an identifier, not a check that recognises a name.
"Lerian STA unavailable since 14:00; response deadline at 19:00"
Required by attach_transfer; ignored otherwise. Lerian STA is asked to confirm it belongs to this file before anything is bound.
"eeeeeeee-eeee-eeee-eeee-eeeeeeeeeeee"
Response
OK

