Continue As New

[rmcdaniel]

This PR adds support for “continue as new” workflows, updating core classes, model relations, and tests to enable workflows to restart with new input through a ContinuedWorkflow marker.

• Introduces WorkflowContinuedStatus and a Continues trait to emit a ContinuedWorkflow and transition to the continued state.
• Updates Workflow, WorkflowStub, and StoredWorkflow to handle active/continued workflows, plus new root/active relations.
• Adds fixtures and feature tests for continue-as-new, and adjusts CI/env settings to account for failed queue tables.

[Copilot]

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/States/WorkflowContinuedStatus.php	Adds new continued status class
src/Traits/Continues.php	Implements continueAsNew() logic and promise marker
src/Models/StoredWorkflow.php	Adds continuedWorkflows relation and root/active methods
src/Workflow.php	Handles ContinuedWorkflow in handle()
src/WorkflowStub.php	Routes calls to the active workflow instance
tests/Fixtures/TestContinueAsNewWorkflow.php	New fixture for continue-as-new workflow
tests/Feature/ContinueAsNewWorkflowTest.php	Feature test validating continue-as-new behavior
tests/Unit/States/WorkflowStatusTest.php	Updates state config test to include continued status
tests/TestCase.php	Registers failed queue table migration
tests/.env.unit, tests/.env.feature	Defines QUEUE_FAILED_DRIVER=null
.github/workflows/php.yml	Exports QUEUE_FAILED_DRIVER in CI and adds log artifact

Comments suppressed due to low confidence (1)

.github/workflows/php.yml:78

• Quoting "null" makes it a string in the CI environment. Remove the quotes so that the runner interprets it as a true null value.

        QUEUE_FAILED_DRIVER: "null"

[travisaustin]

It seems that this works well if continueAsNew() is called from a "root" workflow, but not from a child workflow. If continueAsNew() is used in a child workflow, the child workflow completes successfully but the calling worklow is never dispatched again to continue it's processing.

[travisaustin]

I found a solution and created #248. I don't know if this is how you'd prefer to do it, but this seems to work. I also haven't written any tests for it, but maybe this will be helpful for you.

[rmcdaniel]

Thanks! I will get some time to review this tonight. For the most part, I want to follow Temporal's established patterns to maximize compatibility between the two but we can deviate a little if it makes sense. I'm trying to figure out if Temporal supports continueAsNew with child workfllows but it doesn't look like it.

[travisaustin]

Ah, that's interesting that Temporal has that constraint. I appreciate your looking into it.

[rmcdaniel]

@travisaustin I merged in your PR with some changes in the placement of your logic. Everything seems to be working for child workflows as well now.

[travisaustin]

Hey @rmcdaniel! Thanks again for adding this.

Is there any chance you'll include this in an upcoming release?

[rmcdaniel]

@travisaustin Yes sir! I'll try to get it out this weekend.