adding message to response body

Author: nishika26

backend/app/api/docs/llm/get_llm_call.md

@@ -2,43 +2,9 @@ Retrieve the status and results of an LLM call job by job ID.
 
 This endpoint allows you to poll for the status and results of an asynchronous LLM call job that was previously initiated via the POST `/llm/call` endpoint.
 
-### Path Parameters
-
-**`job_id`** (required, UUID) - The unique identifier of the job returned when the LLM call was created.
-
-### Response
-
-The endpoint returns an `LLMJobPublic` object containing:
-
-- **`job_id`** (UUID) - The unique identifier of the job
-- **`status`** (string) - Current status of the job. Possible values:
-  - `PENDING` - Job has been created and is waiting to be processed
-  - `PROCESSING` - Job is currently being processed
-  - `SUCCESS` - Job completed successfully
-  - `FAILED` - Job failed during processing
-- **`llm_response`** (object | null) - The complete LLM response when status is `SUCCESS`, containing:
-  - `response` - Normalized LLM response with provider_response_id, conversation_id, provider, model, and output
-  - `usage` - Token usage information (input_tokens, output_tokens, total_tokens)
-- **`error_message`** (string | null) - Error details if the job failed, otherwise null
-- **`job_inserted_at`** (datetime) - Timestamp when the job was created
-- **`job_updated_at`** (datetime) - Timestamp when the job was last updated
-
-### Usage
-
-1. Create an LLM call using POST `/llm/call` to receive a `job_id`
-2. Use this endpoint to poll for the job status
-3. When the status is `SUCCESS`, the `llm_response` field will contain the complete LLM response
-4. When the status is `FAILED`, check the `error_message` field for details
-
-### Polling Strategy
-
-- Poll this endpoint periodically until `status` is either `SUCCESS` or `FAILED`
-- Use exponential backoff (e.g., 1s, 2s, 4s, 8s) to reduce server load
-- Stop polling when status is terminal (`SUCCESS` or `FAILED`)
 
 ### Notes
 
 - This endpoint returns both the job status AND the actual LLM response when complete
 - LLM responses are also delivered asynchronously via the callback URL (if provided)
 - Jobs can be queried at any time after creation
-- The endpoint returns a 404 error if the job_id does not exist

backend/app/api/routes/llm.py

@@ -75,7 +75,10 @@ def llm_call(
     if not job:
         raise HTTPException(status_code=404, detail="Job not found")
 
-    message = "Your response is being generated and will be delivered via callback."
+    if request.callback_url:
+        message = "Your response is being generated and will be delivered via callback."
+    else:
+        message = "Your response is being generated"
 
     job_response = LLMJobImmediatePublic(
         job_id=job.id,
@@ -85,8 +88,6 @@ def llm_call(
         job_updated_at=job.updated_at,
     )
 
-    # message = "Your response is being generated and will be delivered via callback." if request.callback_url else "Your response is being generated. Use the job_id to poll for results."
-
     return APIResponse.success_response(data=job_response)
 
 
@@ -116,7 +117,8 @@ def get_llm_call_status(
         llm_calls = get_llm_calls_by_job_id(session=session, job_id=job_id)
 
         if llm_calls:
-            # Get the first (latest) LLM call
+            # Get the first LLM call from the list which will be the only call for the job id
+            # since we initially won't be using this endpoint for llm chains
             llm_call = llm_calls[0]
 
             llm_response = LLMResponse(

backend/app/models/llm/response.py

@@ -111,12 +111,12 @@ class LLMJobBasePublic(SQLModel):
 
     job_id: UUID
     status: str  # JobStatus from job.py
-    message: str
 
 
 class LLMJobImmediatePublic(LLMJobBasePublic):
     """Immediate response after creating an LLM job."""
 
+    message: str
     job_inserted_at: datetime
     job_updated_at: datetime