structured_responseTier 1 · 70% confidence
ai-agents-structured-response-each-task-execution-needs-to-return-a-machine-read-ab9eb68a
agent: ai_agents
When does this happen?
IF Each task execution needs to return a machine-readable result (status, duration, data source, summary) and specific error codes on failure.
How others solved it
THEN Define a standard JSON response object with fields: 'status' (success/failed), 'duration', 'data_source', 'summary', and on failure 'error_category' (e.g., 'fetch_failed', 'db_missing', 'notify_failed'). Ensure all execution paths produce this structure. Log the response for observability.
# Pseudocode for structured result
import time, json
def execute_task():
start = time.time()
try:
data = fetch_data() # may raise
result = {
'status': 'success',
'duration': time.time() - start,
'data_source': 'api_x',
'summary': 'Fetched 10 items'
}
except FetchError as e:
result = {
'status': 'failed',
'duration': time.time() - start,
'data_source': 'api_x',
'summary': '',
'error_category': 'fetch_failed',
'error_detail': str(e)
}
# always output
return resultRelated patterns
github
ai-agents-github-support-for-reasoning-in-openrouter-and-deepseek-p-48add6f0
Tier 1 · 40%
githubai-agents-github-server-capabilities-not-affecting-the-stream-of-ca-ca806d9e
Tier 1 · 40%
githubai-agents-github-patrick-von-platen-cd4d7ceb
Tier 1 · 40%
model_loadingai-agents-model-loading-loading-a-gemma-3-checkpoint-with-automodelforcaus-cc5b7a71
Tier 1 · 70%
githubai-agents-github-runtimeerror-cuda-error-cublas-status-not-initiali-9b601119
Tier 1 · 40%
githubai-agents-github-bug-frequent-ide-disconnections-disrupting-workflo-e9f35aca
Tier 1 · 40%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.