Skip to content

Add previous_execution_id field to DatasetRow/scenario#3457

Open
devin-ai-integration[bot] wants to merge 4 commits intomainfrom
devin/1766561060-add-previous-execution-id-to-scenario
Open

Add previous_execution_id field to DatasetRow/scenario#3457
devin-ai-integration[bot] wants to merge 4 commits intomainfrom
devin/1766561060-add-previous-execution-id-to-scenario

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot commented Dec 24, 2025

Adds previous_execution_id field to DatasetRow (scenario) in the SDK, enabling users to reference a previous Workflow Execution for initial State loading. This field is now supported in both the Python SDK and the TypeScript codegen for round-trip serialization.

Updates since last revision:

  • Wired previous_execution_id through WorkflowSandboxRunner.run() to workflow.stream(), so running a sandbox with a dataset row that includes previous_execution_id will now correctly load prior state
  • Added test to verify WorkflowSandboxRunner passes previous_execution_id to the workflow stream

Review & Testing Checklist for Human

  • Verify that running a sandbox with previous_execution_id actually loads state from the previous execution (the unit test only verifies the parameter is passed, not the end-to-end behavior)
  • Confirm the TypeScript codegen generates valid Python code with previous_execution_id parameter

Notes

@devin-ai-integration
Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR that start with 'DevinAI' or '@devin'.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Comment thread ee/codegen/src/__test__/workflow-sandbox.test.ts Outdated
@vincent0426 vincent0426 marked this pull request as ready for review December 24, 2025 17:44
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread ee/codegen/src/generators/workflow-sandbox-file.ts
devin-ai-integration Bot and others added 4 commits December 29, 2025 21:59
Co-Authored-By: vincent@vellum.ai <0426vincent@gmail.com>
Co-Authored-By: vincent@vellum.ai <0426vincent@gmail.com>
Co-Authored-By: vincent@vellum.ai <0426vincent@gmail.com>
Co-Authored-By: vincent@vellum.ai <0426vincent@gmail.com>
@devin-ai-integration devin-ai-integration Bot force-pushed the devin/1766561060-add-previous-execution-id-to-scenario branch from f9ed1ed to 4e706e6 Compare December 29, 2025 22:02
@vincent0426
Copy link
Copy Markdown
Contributor

@codex review

@vellum-ai vellum-ai deleted a comment from chatgpt-codex-connector Bot Dec 29, 2025
@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@dvargas92495
Copy link
Copy Markdown
Contributor

dvargas92495 commented Dec 30, 2025

@TirmanSidhu brought up an interesting point last week where we may be able to infer the previous_execution_id from just loading the latest execution from the sandbox for a given scenario. I'm starting to think we may want to hold off on merging this in the SDK-level/django-level, until we feel the need for persistence after implementing chat triggers from a frontend perspective

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants