Make workflow state (not status) available via API

[robholland]

Is your feature request related to a problem? Please describe. Currently the web UI will show "Running" for cron workflows which are created but not yet started as they are not yet due. This isn't ideal for developers as you can't tell without clicking through to the workflow whether it is actually running.

Describe the solution you'd like It would be better if the web UI was able to refer to the state rather than just the status. Temporal knows that the workflow is created but not yet started, the persistence record has "created" as the state. The state field isn't currently exposed via the Temporal APIs at all, which means this information is not available via tctl either.

[namit-chandwani]

Hey @robholland @yiminc @dnr @samarabbas, I would like to get started with some beginner issue to get familiar with the temporal codebase.

Can you please assign this issue to me if it hasn't been taken up by anyone yet?

[dnr]

This issue is pretty much obsolete since it's about the old "cron" feature. Instead, you could try to get started with some easy schedules bugs. The equivalent bug for schedules might be:

• Schedules with no future action times should show as "Idle" instead of "Running" in the web UI

That one is actually just in the UI though, it can just look at the future action times list and show Idle if it's empty.

In the server, there's one required change to make that work better:

• Schedule "future action times" should respect limited actions

(i.e. if the schedule has one action remaining, it should only list one future action time)

I'm not sure if there are issues filed for those yet but feel free to file them or just send a PR.

[vaibhavyadav-dev]

Hey @dnr, second one, Schedule "future action times" should respect limited actions, already fixed, I've tried it using cli and found expected results.