Report a remote command as done, optionally attaching a zip of the app databases.

Endpointtoday's app

Call: PATCH /gateway/urvi-app-service/api/v1/remote-app-actions/{id}/execution
Service: urvi-app-service
Features: Device registration and remote actions, Sync error log
When: After running a remote action
Auth: X-Sessionid header
In the App Service: POST /devices/{deviceId}/actions/{actionId}/complete

Use case

Online call from DeviceRegistrationViewModel.performAction after a remote command runs. For LOGOUT / CLEAR_APP_DATA, if the offline queue has failed operations the app zips its databases and sends it as a multipart 'file' part (support diagnostics); on success it logs out (and for CLEAR_APP_DATA wipes app data) and returns to Splash. Other action types are just marked completed. Exceptions are swallowed, so the action stays pending and is re-fetched next start.

Headers

Header	Value	Notes
`X-SESSIONID`	<session token>	Passed explicitly as a Retrofit @Header from AndroidSessionManager.sessionId; AuthInterceptor also re-auths and retries once on 401/400.
`Content-Type`	multipart/form-data (only when a zip is attached)	Two Retrofit overloads: multipart with file, or plain PATCH.

Parameters

Param	In	Required	Example	Notes
`remoteAppActionId`	path	Yes	`31`	From the GET list.
`executionStatus`	query	Yes	`EXECUTION_STATUS.COMPLETED`	Always COMPLETED.
`appExecutionDateTime`	query	Yes	`1780000000000`	Now, epoch ms.

Request

Example request body (synthetic data)

{
  "file": "<multipart part: app-data.zip (optional)>"
}

Field	Type	Required	Notes
`file`	binary (zip)	No	Present only when the sync queue has unevaluated ops with attemptCount > 0 (ZipUtil.zipAppDataAndReturnFile).

Response

Example response body (synthetic data)

{
  "id": 31,
  "actionType": "LOGOUT",
  "executionStatus": "EXECUTION_STATUS.COMPLETED"
}

Field	Type	Required	Notes
`(body)`	RemoteAppActionDto		Not read; only isSuccessful matters.

Errors

Status	When	What the app does
`401 / 400`	Session token expired	AuthInterceptor invalidates the token, gets a fresh session id and retries the request once.
`any non-2xx`	Other failures	No logout happens; action remains pending on the server and is fetched again next time.

Source

app/src/main/java/org/platformcommons/urvi/datasource/network/retrofit/APIInterface.kt
app/src/main/java/org/platformcommons/urvi/view/deviceregistration/DeviceRegistrationViewModel.kt