temporalio / temporalio/ui

Ability to search by activity id

Open
#3,249 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
431
Forks
179
Avg merge
2d 9h
Merged PRs (30d)
71

Description

Is your feature request related to a problem? Please describe.

I am using the Java SDK. In my logs I might see something like this:

Activity failure. ActivityId=a1d54128-ac9f-3ba8-bad6-d780bfebb47c, activityType=Foo, attempt=2

However, when attempting to find the workflow in the UI that this activity belongs to, this information is useless.

Describe the solution you'd like

I should be able to find workflows that contain a given activity ID.

Describe alternatives you've considered

The Java SDK could include more context on the warning message for activity failures, which would allow finding the relevant workflow.

This is also related to https://github.com/temporalio/ui/issues/884 in the sense that at least with 884 we could show the workflows with failing activities, which would at least be more helpful than the current situation.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by tracing the existing workflow search UI and its request path, then determine how activity IDs can be searched; done means a given activity ID identifies the workflows containing it in the UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript
Domain
frontend, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.