The protobuf package voplica.types.notification: 0 services, 20 messages and 2 enums, defined in voplica/types/notification/notification.proto.
Notification for a comment.
| Field |
Number |
Type |
Label |
Description |
| comment_id |
1 |
string |
|
|
| commenter_id |
2 |
string |
|
From whom |
| resource_id |
3 |
string |
|
ID of the post or resource commented on. |
| comment |
4 |
string |
|
|
Notification for a content moderation state change (e.g. auto-flagged + force-unpublished,
or an admin decision). Carries ids + status only; the client re-fetches the content for details.
Notification for dataset preparation run status change. Carries only ids + status; the
client re-fetches the run/preparation for details.
| Field |
Number |
Type |
Label |
Description |
| dataset_id |
1 |
string |
|
|
| status |
2 |
voplica.types.base.JobStatus |
|
|
| message |
3 |
string |
optional |
If status is FAILED it may contain error message here. |
| preparation_id |
4 |
string |
|
The mutable preparation the run writes into. |
| preparation_run_id |
5 |
string |
|
The preparation run whose status changed. |
Notification for file upload status change.
| Field |
Number |
Type |
Label |
Description |
| file_id |
1 |
string |
|
|
| status |
2 |
voplica.types.file.upload.FileUploadStatus |
|
|
| asset_id |
3 |
string |
optional |
If status is COMPLETED is will contain asset id to which the uploaded file was assigned |
| message |
4 |
string |
optional |
If status is FAILED it may contain error message here. |
Notification for a “like” event.
| Field |
Number |
Type |
Label |
Description |
| liker_id |
1 |
string |
repeated |
ID of the user who liked a specific resource. If many users liked then this may contain several user ids, but not necessary all ids. This is useful to show notification like: userA, userB, userC and 12345 more users liked you post. |
| resource_id |
2 |
string |
|
ID of the post or resource that was liked. |
| counter |
3 |
int64 |
|
How many users liked your resource since last update. This is not a total amount of likes, but simply difference from the last notification about this resource. |
Notification for a new direct message.
| Field |
Number |
Type |
Label |
Description |
| message_id |
1 |
string |
|
|
| from_user_id |
2 |
string |
|
|
| message |
3 |
string |
|
|
Notification for model training job status change.
| Field |
Number |
Type |
Label |
Description |
| model_training_job_id |
1 |
string |
|
|
| status |
2 |
voplica.types.base.JobStatus |
|
|
| message |
3 |
string |
optional |
If status is FAILED it may contain error message here. |
| model_training_run_id |
4 |
string |
optional |
The run whose lifecycle produced this status, when the change is run-scoped (started / terminal). Empty for pure job-level changes. |
Notification that a new training checkpoint was saved and registered. Carries ids + step
only; the client re-fetches the checkpoint (hydrated) via GetModelTrainingCheckpoint /
ListModelTrainingCheckpoints.
| Field |
Number |
Type |
Label |
Description |
| model_training_job_id |
1 |
string |
|
|
| model_training_run_id |
2 |
string |
|
|
| checkpoint_id |
3 |
string |
|
|
| step |
4 |
uint64 |
|
Training step at which the checkpoint was saved. |
| model_variant_id |
5 |
string |
optional |
The ModelVariant minted for this checkpoint, when the job trains into an output model. |
Notification that a new group of samples was generated during model training. Carries ids
- step only; the client re-fetches the group with a files retriever to render previews.
| Field |
Number |
Type |
Label |
Description |
| model_training_job_id |
1 |
string |
|
|
| model_training_run_id |
2 |
string |
|
|
| samples_group_id |
3 |
string |
|
|
| step |
4 |
uint64 |
|
Training step at which the samples were generated. |
| samples_count |
5 |
uint32 |
|
|
| checkpoint_id |
6 |
string |
optional |
Checkpoint the group was produced alongside (sample-after-save), when any. |
Live training progress snapshot. Unlike the id-only notifications above this embeds the
(small) stats payload so dashboards can render progress without a follow-up read; metric
HISTORY still comes from ListModelTrainingMetricsPoints. Server-side throttled.
Notification for dataset preparation status change.
| Field |
Number |
Type |
Label |
Description |
| notification_id |
1 |
string |
|
Unique ID for the notification. |
| timestamp |
2 |
int64 |
|
Unix timestamp when notification was created |
| status |
3 |
NotificationStatus |
|
If notification was seen already by the user or not |
| payload |
4 |
NotificationPayload |
|
payload of a specific notification type |
Notification for payment status update.
| Field |
Number |
Type |
Label |
Description |
| enforcement |
1 |
voplica.types.file.upload.quota.StorageEnforcementState |
|
|
| over_by_bytes |
2 |
uint64 |
|
Bytes over the personal ceiling at the moment of the transition, 0 when back under. |
| grace_expires_at |
3 |
uint64 |
|
When the grace ends (epoch millis), 0 when not applicable. |
| personal_limit_bytes |
4 |
uint64 |
|
The ceiling that was exceeded, so the message can say “of 100 GB” without a second call. |
| notice_text |
5 |
string |
|
|
Notification for payment status update.
Notification for workflow execution status change.
Sent when the workflow execution transitions between states (PENDING -> RUNNING -> COMPLETED/FAILED/CANCELLED).
Notification that a step iteration within a workflow execution has completed and produced output.
This enables real-time partial results: clients can fetch full output data via GetWorkflowStepOutputs API.
Does NOT include the full output data (could be large) - only identifiers for the client to fetch if needed.
| Field |
Number |
Type |
Label |
Description |
| workflow_execution_id |
1 |
string |
|
|
| step_id |
2 |
uint32 |
|
|
| iteration_number |
3 |
uint32 |
|
|
| step_status |
4 |
voplica.types.base.JobStatus |
|
Status of the step iteration (COMPLETED or FAILED). |
| Name |
Number |
Description |
| NOTIFICATION_STATUS_UNSPECIFIED |
0 |
|
| UNSEEN |
1 |
|
| SEEN |
2 |
|
| Name |
Number |
Description |
| SUPPORT_ISSUE_UPDATE_KIND_UNSPECIFIED |
0 |
|
| SUPPORT_ISSUE_UPDATE_REPLIED |
1 |
|
| SUPPORT_ISSUE_UPDATE_CLOSED |
2 |
|
| SUPPORT_ISSUE_UPDATE_REOPENED |
3 |
an admin reply on a closed issue |