@TERADA, Tomohiko (寺田 智彦) I can confirm that there has been a bug with batch jobs that caused the metadata property to be null. A fix has been deployed now and I can see metadata property returns with the data added in the create job. Please see a response of my batch job that was submitted today which contains the metadata.
{
"cancelled_at": null,
"cancelling_at": null,
"completed_at": 1726573123,
"completion_window": "24h",
"created_at": 1726572674,
"error_file_id": "file-4ec49c3f-10e2-429d-aefd-f5b2e38998c5",
"expired_at": null,
"expires_at": 1726659073,
"failed_at": null,
"finalizing_at": 1726573054,
"id": "batch_033b4cc2-d00c-4df9-967e-fccde36e6578",
"in_progress_at": 1726572839,
"input_file_id": "file-380cd850c29947b695bca88a7006bcae",
"errors": null,
"metadata": {
"modified": "true",
"user": "abc123"
},
"object": "batch",
"output_file_id": "file-bbb36a01-497e-42c8-88a7-b2e68ecef292",
"request_counts": {
"total": 3,
"completed": 3,
"failed": 0
},
"status": "completed",
"endpoint": "/chat/completions"
}
Could you please retry with a new job and check if it is working as expected for you. Thanks!!
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.