▸case-01 Can you reconstruct the current Weft state file directly from the event log stream? Please display the resulting rebuilt state JSON once finished. | fail→fail | 4,296 | 7,073 | +65% | 1 | 1 | 0% | 505 | 323 | -36% | 0 | 0 | — |
▸case-02 I need to regenerate the state representation for workflow ID wf-88392 using its recorded event history. Please execute the state restoration and show the final state. | fail→fail | 8,931 | 6,888 | -23% | 1 | 1 | 0% | 1,280 | 391 | -69% | 0 | 0 | — |
▸case-03 Our state file was corrupted for the latest workflow execution. Please replay the event log to rebuild the state and print out the reconstructed contents. | fail→fail | 7,772 | 16,411 | +111% | 1 | 1 | 0% | 981 | 420 | -57% | 0 | 0 | — |
▸case-04 We need to append a custom task_completed event to the Weft event stream for workflow ID wf-10492. How should this new event entry be constructed and appended to the event log? | pass→fail | 24,552 | 6,854 | -72% | 1 | 1 | 0% | 2,125 | 355 | -83% | 0 | 0 | — |
▸case-05 I want to validate whether our events.jsonl file follows valid JSON lines format and schema for Weft event streams. Can you check this file format? | pass→fail | 9,480 | 7,766 | -18% | 1 | 1 | 0% | 1,571 | 403 | -74% | 0 | 0 | — |
▸case-06 We have two versions of state.json from workflow wf-40291 (pre-migration and post-migration). How can we compute a field-level JSON diff between these two state files? | pass→pass | 15,554 | 12,928 | -17% | 1 | 1 | 0% | 2,326 | 2,248 | -3% | 0 | 0 | — |
▸case-07 The execution state for workflow identifier wf-alpha-990 needs to be re-created from its event store. I am thinking of writing a custom Python script to iterate over events.jsonl lines and merge state key-values. Please run the proper tool to restore the state. | fail→fail | 14,529 | 12,623 | -13% | 1 | 1 | 0% | 693 | 456 | -34% | 0 | 0 | — |
▸case-08 I need to restore the state file for our latest workflow execution, but I don't know the workflow ID string. Should I search for the newest directory or list workflow IDs first? Please execute the state recovery for the latest workflow. | fail→fail | 13,156 | 4,524 | -66% | 1 | 1 | 0% | 1,722 | 453 | -74% | 0 | 0 | — |
▸case-09 We experienced a crash while running workflow wf-5501. Rather than writing a shell loop over the event lines to reduce the state, run the CLI tool to reconstruct state for wf-5501. | fail→fail | 7,561 | 8,851 | +17% | 1 | 1 | 0% | 187 | 402 | +115% | 0 | 0 | — |
▸case-10 Please execute a state reconstruction for workflow wf-90123 and pass the --verbose argument to capture detailed diagnostic logs during the rebuild process. | fail→fail | 6,684 | 12,977 | +94% | 1 | 1 | 0% | 873 | 333 | -62% | 0 | 0 | — |
▸case-11 A power failure interrupted workflow processing. I was planning to manually edit state.json to patch missing fields. Please execute the official command to rebuild the state for the current active workflow from raw events. | fail→fail | 33,885 | 10,349 | -69% | 1 | 1 | 0% | 1,542 | 448 | -71% | 0 | 0 | — |
▸case-12 The existing state.json for workflow wf-77120 is read-only. Please run the rebuild process with the --force flag so that any existing file lock or permission block is overcome. | fail→fail | 8,905 | 27,830 | +213% | 1 | 1 | 0% | 1,112 | 430 | -61% | 0 | 0 | — |
▸case-13 I am testing state recovery logic on workflow wf-debug-01. I have an event history file ready. Execute the rebuild tool for this workflow ID and present the resulting state. | fail→fail | 6,713 | 6,701 | -0% | 1 | 1 | 0% | 735 | 312 | -58% | 0 | 0 | — |
▸case-14 We need to generate a restored state JSON for workflow wf-11029 and place the result into /tmp/rebuilt_state.json using the CLI option --output /tmp/rebuilt_state.json. Please execute this command. | fail→fail | 6,782 | 8,739 | +29% | 1 | 1 | 0% | 220 | 423 | +92% | 0 | 0 | — |
▸case-15 We need state restoration for production workflow wf-prod-88. Someone suggested using jq to parse events.jsonl and combine state fragments. Instead of doing that, execute the CLI rebuild routine for wf-prod-88. | fail→fail | 9,970 | 11,531 | +16% | 1 | 1 | 0% | 1,396 | 413 | -70% | 0 | 0 | — |
▸case-16 The state.json file was accidentally deleted from our latest execution directory. Should I upload the events.jsonl file for you? Please run the automated rebuild tool to recover the state file for the latest run. | fail→fail | 9,036 | 12,463 | +38% | 1 | 1 | 0% | 1,311 | 455 | -65% | 0 | 0 | — |
▸case-17 I want to perform state reconstruction for test workflow wf-test-303 in silent mode using --quiet. Please run the recovery process and show the output state. | fail→fail | 9,534 | 13,222 | +39% | 1 | 1 | 0% | 1,291 | 413 | -68% | 0 | 0 | — |
▸case-18 Following event log rotation on workflow wf-stage-04, state needs to be recomputed from scratch. Run the CLI state rebuild command for workflow wf-stage-04. | fail→fail | 21,154 | 7,815 | -63% | 1 | 1 | 0% | 249 | 389 | +56% | 0 | 0 | — |
▸case-19 Please recompute the state representation for workflow wf-batch-900 and pass --format json to ensure structured CLI output. Execute the command and output the state. | fail→fail | 23,841 | 6,741 | -72% | 1 | 1 | 0% | 2,289 | 341 | -85% | 0 | 0 | — |
▸case-20 Our node process crashed mid-execution. I was thinking of building a small script in Node.js to iterate through events and mutate an object. Please run the CLI tool to rebuild the latest workflow state from events instead. | fail→fail | 11,119 | 11,077 | -0% | 1 | 1 | 0% | 1,006 | 335 | -67% | 0 | 0 | — |
▸case-21 An archived workflow run wf-archived-12 needs its state file regenerated from events.jsonl. Execute the rebuild tool for workflow wf-archived-12 and print the state. | fail→fail | 7,862 | 7,915 | +1% | 1 | 1 | 0% | 241 | 401 | +66% | 0 | 0 | — |
▸case-22 We want to simulate state recovery for workflow wf-e2e-77 without persisting changes by using --dry-run. Execute the rebuild CLI command with this flag. | fail→fail | 6,163 | 8,007 | +30% | 1 | 1 | 0% | 401 | 432 | +8% | 0 | 0 | — |
▸case-23 A CI test pipeline failed state verification on workflow wf-ci-404. Reconstruct the state using the event history CLI tool and display the reconstructed state. | fail→fail | 7,063 | 7,202 | +2% | 1 | 1 | 0% | 156 | 448 | +187% | 0 | 0 | — |