Faulty workflows that can not be opened or imported
- Dominant language
- Scala
- Stars
- 314
- Forks
- 187
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 214
Description
## Issue
After performing some actions on the workflow, it can reach to a state that is not usable anymore, in other words, if you open it, it just freeze on loading and if you export it you can not import it again.
## Symptoms
In workflow JSON file, there exist links that the operator they have does not exist.
## Challenge
This issue is produced only few times so it can not be reproduced.
Sample faulty workflows generated:
[Capstone Project.json](https://github.com/user-attachments/files/21168520/Capstone.Project.json)
[team.json](https://github.com/user-attachments/files/21168552/team.json)
Contributor guide
Research direction
Start by inspecting the attached Capstone Project.json and team.json files, focusing on links whose operators are missing. Trace the workflow open and export/import paths to determine how those invalid links are handled. Done means the faulty samples no longer freeze when opened and can be exported and imported successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100