Hi, We would like to collect run history logs using the Job Scheduler API. It would be very helpful if the response included the workspaceId. This would allow us to store the raw JSON response as-is in our Lakehouse while still being able to identify which workspace each item belongs to. Without the workspaceId in the response, we need to maintain an external mapping between items and workspaces, which adds unnecessary complexity and potential for inconsistency. Including the workspaceId would make the response self-contained and easier to manage in downstream ingestion and auditing scenarios. Current response sample: { "id": "f2d65699-dd22-4889-980c-15226deb0e1b", "itemId": "431e8d7b-4a95-4c02-8ccd-6faef5ba1bd7", "jobType": "DefaultJob", "invokeType": "Manual", "status": "Completed", "rootActivityId": "8c2ee553-53a4-7edb-1042-0d8189a9e0ca", "startTimeUtc": "2023-04-22T06:35:00.7812154", "endTimeUtc": "2023-04-22T06:35:00.8033333", "failureReason": null }
... View more