Skip to content

[Fix #1151] Replace output with outputUri in lifecycle completed events #1172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ricardozanini wants to merge 6 commits into
base: main
Choose a base branch
from
+4 −10
Open

[Fix #1151] Replace output with outputUri in lifecycle completed events #1172

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
e02836f
[Fix #1151] Replace output with outputUri in lifecycle completed events
ricardozanini Jul 23, 2026
b43f060
Consider co-pilot's review
ricardozanini Jul 23, 2026
ab35e67
Potential fix for pull request finding
ricardozanini Jul 23, 2026
5c6b59b
Merge branch 'main' into fix/1151-lifecycle-event-output-reference
ricardozanini Jul 23, 2026
06ccaee
Potential fix for pull request finding
ricardozanini Jul 23, 2026
04de1fd
Merge branch 'main' into fix/1151-lifecycle-event-output-reference
ricardozanini Jul 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 4 additions & 10 deletions dsl-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1450,17 +1450,14 @@ The data carried by the cloud event that notifies that a workflow ran to complet
|:--|:---:|:---:|:---|
| name | `string` | `yes` | The qualified name of the workflow ran to completion. |
| completedAt | `dateTime` | `yes` | The date and time at which the workflow ran to completion. |
| output | `map` | `no` | The workflow's output, if any. |
| outputUri | `uri` | `no` | A URI pointing to the workflow's output data, if any. This follows the [Claim Check](https://www.enterpriseintegrationpatterns.com/patterns/messaging/StoreInLibrary.html) pattern to avoid embedding large payloads in the event; events larger than 64 KiB are not guaranteed to be forwarded by intermediaries per the [CloudEvents size limits](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#size-limits). |

###### Examples

```yaml
name: orderPetWorkflow-ix7iryakiem8j.samples
completedAt: '2024-07-26T16:59:57-05:00'
output:
orderId: '0a7f8581-acb9-4133-a378-0460c98ea60c'
petId: xt84hj202q14s
status: placed
outputUri: https://workflow-engine.example.com/workflows/orderPetWorkflow-ix7iryakiem8j/output
```

##### Workflow Status Changed Event
Expand Down Expand Up @@ -1641,18 +1638,15 @@ The data carried by the cloud event that notifies that a task ran to completion.
| workflow | `string` | `yes` | The qualified name of the workflow the task that ran to completion belongs to. |
| task | `uri` | `yes` | A JSON Pointer that references the task that ran to completion. |
| completedAt | `dateTime` | `yes` | The date and time at which the task ran to completion. |
| output | `map` | `no` | The task's output, if any. |
| outputUri | `uri` | `no` | A URI pointing to the task's output data, if any. This follows the [Claim Check](https://www.enterpriseintegrationpatterns.com/patterns/messaging/StoreInLibrary.html) pattern to avoid embedding large payloads in the event; events larger than 64 KiB are not guaranteed to be forwarded by intermediaries per the [CloudEvents size limits](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#size-limits). |

###### Examples

```yaml
workflow: orderPetWorkflow-ix7iryakiem8j.samples
task: '/do/1/initialize'
completedAt: '2024-07-26T16:59:57-05:00'
output:
orderId: '0a7f8581-acb9-4133-a378-0460c98ea60c'
petId: xt84hj202q14s
status: placed
outputUri: https://workflow-engine.example.com/workflows/orderPetWorkflow-ix7iryakiem8j/tasks/initialize/output
```

##### Task Status Changed Event
Expand Down
Loading