surface ctx.getHistory() -> { size, stepCount }#206
surface ctx.getHistory() -> { size, stepCount }#206ianmacartney wants to merge 5 commits intoian/resumefrom
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
commit: |
acee365 to
b7fdb37
Compare
9aab249 to
eed620f
Compare
eed620f to
df08ea2
Compare
b7fdb37 to
28c53f9
Compare

Adds workflow history tracking with a new
ctx.getHistory()method to monitor workflow execution metrics.Fixes #178
What changed?
StepExecutorto track workflow execution metrics:journalEntrySizewithjournalSizeand addedstepCountto track both total size and number of stepsgetHistory()method that returns these metricsgetHistory()method to theWorkflowCtxtypecreateWorkflowCtxfunction to accept and expose the history getterHow to test?
ctx.getHistory()sizeandstepCountpropertiesWhy make this change?
This change provides developers with visibility into workflow execution metrics, allowing them to monitor the size and complexity of their workflows. This is particularly useful for debugging performance issues and preventing workflows from hitting size limits unexpectedly. The incremental tracking approach is also more efficient than calculating the entire journal size upfront.