# <a id="bitdrift.public.unary.common.v1.SessionStatusInfo"></a>SessionStatusInfo

**Source definition:** [`src/bitdrift/public/unary/common/v1/common.proto#L114-L134`](<https://github.com/bitdriftlabs/api/blob/main/src/bitdrift/public/unary/common/v1/common.proto#L114-L134>)

<section class="proto-fields-table" markdown>
| Field | Type | Description |
|---|---|---|
| session_soft_deleted | <span class="proto-type proto-type-primitive">bool</span> | If this is true the session is known but has been soft deleted due to account retention policies. Contact support to recover the session if you believe this is in error. |
| session_seen_on_device | <span class="proto-type proto-type-primitive">bool</span> | If this is true, a device has reported seeing this session, but it was never triggered for attempted upload. |
| session_triggered_but_rejected | <span class="proto-type proto-type-primitive">bool</span> | If this is true, the session was triggered but rejected, due to daily limits. |
| session_triggered_and_accepted | <span class="proto-type proto-type-primitive">bool</span> | If this is true, the session was triggered and accepted for upload. As the device can immediately go offline this does not guarantee that the session was uploaded. |
| session_uploaded | <span class="proto-type proto-type-primitive">bool</span> | If this is true, at least some logs for the session were uploaded. If hydration is failing this is likely a very new session and eventual consistency means it has not yet been fully indexed. Try again soon. |

</section>
<p class="h4">Example</p>
<div class="proto-json-blob"><pre><code>{
  "session_seen_on_device": true,
  "session_soft_deleted": false,
  "session_triggered_and_accepted": true,
  "session_triggered_but_rejected": false,
  "session_uploaded": true
}</code></pre></div>

