Skip to content
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

Allow invalidating cache for a specific node / process #3710

Closed
greschd opened this issue Jan 10, 2020 · 1 comment
Closed

Allow invalidating cache for a specific node / process #3710

greschd opened this issue Jan 10, 2020 · 1 comment

Comments

@greschd
Copy link
Member

greschd commented Jan 10, 2020

In addition to implementing a way of invalidating cache on a per-exit-code level or on the level of the process class, I think there should be a way to mark a specific node / process as invalid.

The use case for this is when a workflow fails with a random calculation failure. If the calculation remains a valid cache, re-running the workflow would just immediately fail.
Previously I would just delete the offending calculation, but due to the new traversal / deleting rules, this now deletes the entire workflow tree.

The obvious "correct" way of solving such issues is through marking exit codes and using restart workchains, but it's difficult to get this right in 100% of cases - making this escape hatch very useful.

This could probably be implemented fairly easily through an updatable attribute.

Mentioning @sphuber for comment.

@sphuber
Copy link
Contributor

sphuber commented Jun 1, 2024

This feature was added in #5207

@sphuber sphuber closed this as completed Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants