Continue Team Run
Continue a paused or incomplete team run with updated requirements.
Use Cases:
- Resume execution after tool approval/rejection
- Provide manual tool execution results
- Resume after admin approval (requirements can be empty; resolution fetched from DB)
Requirements Parameter: JSON string containing array of requirement objects with tool execution results. Can be empty when an admin-required approval has been resolved.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Continuation boundary. Use 'end', 'last_user', or a numeric message index.
Response
A non-streaming run response or a server-sent event stream. Streaming execution failures are delivered as events after the stream starts.
Unique identifier for the team run
Parent run ID if this is a nested run
Team ID that executed this run
Run status (PENDING, RUNNING, COMPLETED, ERROR, etc.)
Output content from the team run
Reasoning content if reasoning was enabled
List of reasoning steps
Input provided to the run
Format of the response (text/json)
Performance and usage metrics
Tools used in the run
Message history for the run
Events generated during the run
Run creation timestamp
References cited in the run
Citations from the model (e.g., from Gemini grounding/search)
Reasoning process messages
Session state at the end of the run
Input media attachments
Images included in the run
Videos included in the run
Audio files included in the run
Files included in the run
Audio response if generated
Followup suggestions generated after the run
If this team run was forked from another run, the source run's ID
If this team run was forked, the message index at which the source was truncated
If this team run was created via session branch, the source session's ID
If this team run was produced via regenerate=true, the source run's ID
Message index of the most recent mid-run checkpoint (checkpoint='tool-batch' runs)