You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add sleep-for-days sample
* address pr comments
* WhenAny -> WhenAnyAsync
* fixed test - added check for sleep timer start before time-skipping
* ran dotnet format
* changed [Fact] -> [TimeSkippingServerFact]
* use to check for eventuality of timer history event
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ Prerequisites:
30
30
*[Saga](src/Saga) - Demonstrates how to implement a saga pattern.
31
31
*[Schedules](src/Schedules) - How to schedule workflows to be run at specific times in the future.
32
32
*[SignalsQueries](src/SignalsQueries) - A loyalty program using Signals and Queries.
33
+
*[SleepForDays](src/SleepForDays/) - Use a timer to send an email every 30 days.
33
34
*[Timer](src/Timer) - Use a timer to implement a monthly subscription; handle workflow cancellation.
34
35
*[UpdateWithStartEarlyReturn](src/UpdateWithStartEarlyReturn) - Use update with start to get an early return, letting the rest of the workflow complete in the background.
35
36
*[UpdateWithStartLazyInit](src/UpdateWithStartLazyInit) - Use update with start to lazily start a workflow before sending update.
This sample demonstrates how to create a Temporal workflow that runs forever, sending an email every 30 days.
4
+
5
+
To run, first see [README.md](../../README.md) for prerequisites. Then, run the following from this directory in a separate terminal to start the worker:
6
+
7
+
dotnet run worker
8
+
9
+
Then in another terminal, run the workflow from this directory:
10
+
11
+
dotnet run workflow
12
+
13
+
The worker terminal will show logs from running the workflow.
0 commit comments