René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: `runs.retrieve()` is missing `requestOptions` param","articleBody":"### Is your feature request related to a problem? Please describe.\n\nHi there! :)\n\nSome methods like `tasks.trigger()` do accept a `requestOptions` param (the 4th in this case, `TriggerApiRequestOptions`). This supports for example setting `{ clientConfig: ... }`.\n```\nawait tasks.trigger(taskId, undefined, { tags: ['...'] }, { clientConfig: { accessToken } })\n```\n\nOthers however do not accept any clientConfig:\n```\nawait runs.retrieve(runId, ) \u003c- does not accept `requestOptions`\n```\n\nI was wondering if this was by choice or just missing parameters/types. \nBecause in my case, I cannot use the `configure()` method to apply the `accessToken`. I have two trigger projects which I both use in my project. Since I have parallel requests (React server actions), the `configure()` is not correctly applied to the requests, even though if I call it directly before each request.\n\n### Describe the solution you'd like to see\n\nIf this is a mistake, than this is a feature request and Ideally, all SDK API methods would be streamlined to support the `requestOptions` param.\n\n### Describe alternate solutions\n\n- I currently use the HTTP API directly with fetch now. However, I noticed that the [docs](https://trigger.dev/docs/management/runs/retrieve#response-status) on these seem outdated, the status enum documented differs from what the `4.1.0` SDK returns as types. \n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/madebyfabian","@type":"Person","name":"madebyfabian"},"datePublished":"2025-12-08T16:15:25.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2769/trigger.dev/issues/2769"}