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

When restarting a workflow, it doesn't go to processing state and it returns empty workflow object #647

Open
drjova opened this issue Dec 19, 2024 · 5 comments
Assignees

Comments

@drjova
Copy link
Contributor

drjova commented Dec 19, 2024

No description provided.

@drjova
Copy link
Contributor Author

drjova commented Dec 19, 2024

Screenshot 2024-12-19 at 15 59 50

@DonHaul
Copy link
Collaborator

DonHaul commented Dec 19, 2024

where is this restart coming from? if its from https://workflows.inspire.dev.siscern.org/ it seems that its going back to processing

@DonHaul DonHaul self-assigned this Dec 20, 2024
@DonHaul
Copy link
Collaborator

DonHaul commented Dec 20, 2024

when restarting the workflow via the restart workflow button in https://inspirebeta.net/backoffice/6972fef5-4a4a-4191-a4b9-4c728f06a53e the workflow gets restarted without the "workflow" field

@drjova
Copy link
Contributor Author

drjova commented Dec 20, 2024

Yes, it’s from the back office, but the interface doesn’t have the correct state. And if you refresh, you are still getting an error instead of processing.

DonHaul added a commit to DonHaul/inspirehep that referenced this issue Dec 20, 2024
DonHaul added a commit to DonHaul/inspirehep that referenced this issue Dec 20, 2024
DonHaul added a commit to DonHaul/inspirehep that referenced this issue Dec 20, 2024
DonHaul added a commit to DonHaul/inspirehep that referenced this issue Dec 20, 2024
DonHaul added a commit to DonHaul/inspirehep that referenced this issue Dec 20, 2024
DonHaul added a commit to inspirehep/inspirehep that referenced this issue Dec 20, 2024
@DonHaul
Copy link
Collaborator

DonHaul commented Dec 20, 2024

fixed issue on backoffice. it still needs to be fixed in the fronted as after clicking restart to page still gets emptied. After refreshing it all is well.
It takes a bit of time from the state to go back to running, as this only happens when the dag is indeed restarted, should the status be set to StatusChoices.PROCESSING while the dag doesnt start?

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

2 participants