# IRPCVault.SendPushDataPendingHeartbeat

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Vault API](https://developer.m-files.com/APIs/gRPC-API/vault/index.md) > [Vault information](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/SendPushDataPendingHeartbeat/

Badges: `Vault API / core` `write` `session` `returns metadata structure version`

Sends a heartbeat signal as an early response for server data push (with non-zero request id). If the client cannot provide final response in 20 seconds, the client should be sending a heartbeat signal for server that prevents server from terminating the request.

- **Service:** [Vault information](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/index.md) `MFiles.IRPCVault`
- **gRPC method:** `/MFiles.IRPCVault/SendPushDataPendingHeartbeat`
- **HTTP (mf-http-grpc):** `POST /grpc/v1/send-push-data-pending-heartbeat`
- **Request:** [`SendPushDataPendingHeartbeatRequest`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/SendPushDataPendingHeartbeat/index.md#request)
- **Response:** [`SendPushDataPendingHeartbeatResponse`](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/SendPushDataPendingHeartbeat/index.md#response)
- **Book and level:** Vault API, core
- **Kind:** write
- **Session:** Required: the session ID from LogIn in the mfiles-session-id-bin metadata.
- **Idempotent:** no
- **Returns metadata structure version:** yes (in the mfiles-metadata-version-bin trailer)
- **Streaming:** none (unary)

<a id="remarks"></a>

## Remarks

Part of server data push. A client that needs more time to answer a push request sends this
within 20 seconds, and again as needed, so that the server keeps waiting for
[SendPushDataResponse](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/SendPushDataResponse/index.md).

<a id="request"></a>

## Request: SendPushDataPendingHeartbeatRequest

> Nested message fields are expanded to depth 3; follow a type link for deeper levels and for the type's own page.

| Field | Type | Description |
|---|---|---|
| `response_id` | `int32` | The response id, should match with the request id that was received from of the RequestPushDataAsync call. |

<a id="response"></a>

## Response: SendPushDataPendingHeartbeatResponse

No fields.

<a id="related"></a>

## Related methods

- [SendPushDataResponse](https://developer.m-files.com/APIs/gRPC-API/Reference/MFiles.IRPCVault/SendPushDataResponse/index.md): Sends a response for server data push. This is a response for request received with RequestPushDataAsync call (with non-zero request id). This call completes the push data cycle.