Skip waiting for
Access control
- Restricted tokens need the API scope
api.everything_else
/v1/sessions/id/{session_id}/ingestion/skipAuthorizationBearer token · headerrequiredsession_idstringrequiredX-Roboto-Org-IdstringX-Roboto-User-Idstringapplication/jsonfile_idsstring[]requiredOK
dataobjectrequiredResponse of POST /v1/sessions/id/<session_id>/ingestion/skip.
Show propertiesHide properties
ingestionSessionIngestionStatusrequiredWhere a session stands in ingestion, with the files it is still waiting for.
Response of GET /v1/sessions/id/<session_id>/ingestion.
Show propertiesHide properties
session_idstringrequiredstateSessionIngestionStaterequiredWhere a session's ingestion stands.
in_progressprocessingingestedingestion_countintegerrequiredpending_filesPendingIngestionFile[]Show propertiesHide properties
PendingIngestionFilefile_idstringrequiredrelative_pathstringrequiredingestion_statusIngestionStatusrequiredEnumeration of file ingestion status values in the Roboto platform.
Ingestion status tracks whether a file's data has been processed and extracted into topics for analysis and visualization. This status determines what platform features are available for the file and whether it can trigger automated workflows.
File ingestion happens as a post-upload processing step. Roboto supports many common robotics log formats (ROS bags, MCAP files, ULOG files, etc.) out-of-the-box. Custom ingestion actions can be written for other formats.
When writing custom ingestion actions, be sure to update the file's ingestion status to mark it as fully ingested. This enables triggers and other automated workflows that depend on complete ingestion.
Ingested files have first-class visualization support and can be queried through the topic data system.
not_ingestedpartly_ingestedingesteduploadedstring<date-time> | nullShow propertiesHide properties
string<date-time>nulllast_runIngestionRun | nullShow propertiesHide properties
file_idstringrequiredrule_idstringrequiredtrigger_idstringrequiredstartedstring<date-time>requiredstatusIngestionRunStatusrequiredWhere one run of a rule's trigger on a file stands.
runningfailedfinishedinvocation_idstring | nullShow propertiesHide properties
stringnulldetailstring | nullShow propertiesHide properties
stringnullnullpending_file_countintegeringested_file_countintegernot_ingestable_file_countintegerskipped_filesSkippedIngestionFile[]Show propertiesHide properties
SkippedIngestionFilefile_idstringrequiredrelative_pathstringrequiredskipped_atstring<date-time> | nullShow propertiesHide properties
string<date-time>nullskipped_bystring | nullShow propertiesHide properties
stringnullskipped_file_countintegernot_in_sessionstring[]Thrown when the conversation context (messages, system prompt, tool results) exceeds the model's context window limit.
The token estimate and the model's context limit are not carried on the exception, so a caller cannot read usage numbers off it.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when authentication fails
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if an operation would exceed a user or org level limit.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if a user is attempting to perform an action unrecognized by the Roboto platform.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if there is a conflict between a resource you're creating and another existing resource
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown if a resource is missing or expired.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullAn error the platform reported that this SDK release cannot resolve to a specific exception class.
Reported for an element of a :py:class:~roboto.http.BatchResponse whose error names a code this release
defines no class for, or that arrived without a code, without a message, or as text that is not an
error envelope at all. It carries whatever code and message the platform sent, so a caller handling the
failure still learns what went wrong; when no message could be read, the message is the error's raw text.
The error envelope carries no status code, so http_status_code reports the 500 inherited from
:py:class:RobotoDomainException rather than the status the failure actually had.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown by shimmed out APIs which have not yet been implemented
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when a service is unavailable, such as when it's under heavy load and can't accept new requests. This is expected to be transient and ought to be retried.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when the service times out while processing a request. This is exepcted to be transient and ought to be retried.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | nullThrown when the server cannot complete the request because the response payload exceeds a storage or transport capacity limit (e.g., Lambda response size). This is NOT expected to be transient and should NOT be retried.
errorobjectShow propertiesHide properties
error_codenumbermessagestringstack_tracestring | null