microsoft / microsoft/foundry-dev-tools

FYI: data and responses for Bulk Run

Open
#261 1 comment 0 reactions 1 assignee View on GitHub

@qinezh is already working on this.

Since Sep 9, 2025.

enhancement
Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
42m
Merged PRs (30d)
29

Description

Overview

More of an FYI (maybe a feature suggestion). When doing a "Bulk Run" the data and responses won't be saved unless a "New Version" checkpoint is registered. When switching to another Agent, if no checkpoint is registered after completing the Bulk Run, when switching back, the data and responses will be missing. Sounds obvious, but there was no clear indication that this was the case and I double checked the docs, but didn't see it mentioned (could have missed it tho).

Feature Ideas

As a feature, it might be useful to provide a notification or notice that data and responses won't be saved when attempting to swap Agents. Even better might be to auto-save after any response is returned, that way if something were to happen, there would be at least something saved; probably have to check if config in the checkpoint and current config match. I know that the responses might not make sense to auto save since the current config and the last checkpoint might not be the same, but maybe auto saving manually input data would be worthwhile. Exporting the data to a file certainly would be a way to save one's work, but it would be painful if someone didn't know an input a lot of data without knowing to export before switching (luckily I only had three rows with two columns).

tldr;

  • it's possible to lose the responses or data from a Bulk Run without warning
  • register a checkpoint after Bulk Run returns all responses, saves both input data and responses
  • export input data for Bulk Runs to a file if not running right away
  • a notice about unsaved changes when switching Agents or an auto save feature might be nice

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.