feat: visualize jobs (WIP) #9645
Draft
+1,203
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 12, 2024
AlessioGr
added a commit
that referenced
this pull request
Dec 12, 2024
Requirement for #9645. Dynamic code field resizing currently is broken for line-breaks - need to address that in a future PR.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new Tab to all payload-jobs documents that visualizes jobs in a beautiful graph format, based on job log data.
The graph allows you to easily view the input/output data of each task. For failed tasks, it also displays the error that caused the failure. This visualization helps pinpoint exactly where a job failed and why, making it essential for debugging and optimizing workflows.
Previously, it was difficult to follow the sequence of events in jobs with multiple retries and task runs when only viewing raw job log data.
Future plans
In a future PR, we will implement JSON-based workflows. These bring the benefit that we can also visualize all future or possible past paths a job could have taken. This will be useful if you use conditions that determine which task a job will run, and need to debug and have full clarity over why a job took a certain path.
After that is done, we will allow you to build JSON-based workflows in the Payload Admin Panel, without having to touch any code.