temporalio / temporalio/sdk-java
Expose activity start and completion information to the workflow code.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
The workflow history contains information about the time and identity of the activity worker that started and completed an activity. But this information is not available to the workflow code.
Describe the solution you'd like
Some API to get full information about an activity execution.
Additional context
Here is a slack message that outlines one possible usage of this feature:
Hi, I am running workflows with activities and would like to track in real time when some activity types started and completed exactly and be able from other activities in my workflow to log these start and complete time (because I don't want to introduce the logging capability to all my microservices that are also written in different languages).
Right now I can tell from the workflow about the time my activity was scheduled (which is not the time it was started) and also the time it scheduled back to workflow after activity completion (which is not the actual time activity was completed).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how workflow code currently observes activity scheduling and completion through workflow history, then compare that with the activity start and completion metadata described in the issue. Done means workflow code has an API exposing the activity execution information, including actual start and completion times and the worker identity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100