So we have an order use-case and an external system is expected to process payment, the customer has X days to settle payment using the external system (the amount varies by types from 2-0 days) during this time the order status is Pending-Payment … I was planning to create a workflow that will po…

Sorry, I don’t understand your concerns. After poll timeout is reached the activity will complete/timeout and the workflow can execute whatever cleanup logic is needed. What is not elegant about performing the cleanup logic in a finally block?

[image] What is the best practice for a polling activity? Community Support It depends on how frequently you want to poll. For infrequent polls (every minute or slower) use the server side retry. Specify a RetryPolicy (or RetryOptions for Java) when invoking the activit…

Thanks for the quick reply … So I was thinking of utilizing retry policy for that … the thing I didn’t like that the workflow will display failures of activity when the poll was an actual success and there is no simple way to distinguish between an actual failure to poll (due to conn err or config …

There is another issue @maxim with this approach. After poll timeout is reached and the payment has not been fulfilled there is some cleanup work to be done (remove the payment request) to achieve this with retries i will have to have some code knowing how many retries to expect and if its the las…

Ha, sorry it is I who didn’t understood what you meant … We wrapped the sdk with a generic Simple workflow of a single activity … what you mean is I create a workflow with 2 activities one for polling with retries … and then based on its outcome another activity with cleanup logic. Thanks . Yest t…

I would advise against such a wrapping. It sounds like a good idea, but it just eliminates 90% of Temporal value without much benefit.

I agree that it eliminate most of temporal capabilities … But this is exactly my goal. Make it hard to do complex things and stick to known patterns … At least for the beginning of temporal integration into our codebase. There are 3 scenarios we support … Simple single activity workflow to be e…

The main goal of Temporal is to eliminate the need for “known patterns,” as all these patterns are extremely leaky abstractions. The code maintainability of a 100% Temporal solution is much higher than that of any EDA-based system. I’m talking from my experience with many teams that introduced Temp…

Long polling inside workflows or activities

Community Support

maxim March 13, 2024, 5:11am 2

Topic		Replies	Views
What is the best practice for a polling activity? Community Support go-sdk , activity , polling	20	19964	November 25, 2024
Polling in workflow vs. Activity? Community Support	10	5100	March 1, 2023
Is Temporal inherently not built for long polling? Community Support	5	203	September 21, 2025
Using activities to poll for status Community Support go-sdk , activity , polling	1	1139	March 18, 2024
Best practice for handling lost external events and resuming paused workflows Community Support java-sdk , polling	24	424	December 3, 2025

Long polling inside workflows or activities

Related topics