Skip to content

bug: [v4] batchTriggerAndWait cached values are returned as success, no matter what their original value was #2015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cachho opened this issue May 1, 2025 · 1 comment

Comments

@cachho
Copy link

cachho commented May 1, 2025

Provide environment information

System:
OS: Linux 5.15 Ubuntu 20.04.6 LTS (Focal Fossa)
CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
Memory: 6.49 GB / 15.59 GB
Container: Yes
Shell: 3.7.1 - /usr/bin/fish
Binaries:
Node: 18.20.8 - ~/.local/share/nvm/v18.20.8/bin/node
npm: 10.8.2 - ~/.local/share/nvm/v18.20.8/bin/npm
pnpm: 8.6.3 - ~/.local/share/pnpm/pnpm

Describe the bug

Image

In the SDK, these runs don't appear as child runs at all.

Reproduction repo

not available

To reproduce

not at the moment

Additional information

How can I reliably show my users, how many of their sub tasks failed, while in progress/before I get the final output? Without idempotency I can check the status of the run.relatedRuns.children, but tasks that are cached do not appear in this array.

@cachho
Copy link
Author

cachho commented May 1, 2025

as far as I can tell, the run object returned by runs.retrieve contains no info about any cached child runs. So there's no way to show progress until it's completed and you can validate the output.

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

No branches or pull requests

1 participant