Activity scheduled but not started (need help)

Community Support
21

Hey folks,
encountered similar issue when testing out few workflows myself. Sharing the details in my case to help debug further:

As you can see the later workflow succeeded while the earlier one is stuck.

Screenshot 2022-06-19 at 2.10.25 AM
Screenshot 2022-06-19 at 2.10.25 AM3338×300 58.7 KB

History for the stuck workflow is as follows. The last activity that was marked started… executed successfully based on the workflow logs. However, I can see following error in the logs just around the time activity processing succeeded.
Task processing failed with error → Error: context deadline exceeded

Screenshot 2022-06-19 at 2.11.22 AM
Screenshot 2022-06-19 at 2.11.22 AM2380×1110 247 KB

To give more context the activity is not doing any heavy compute operation but a simple DB update.

Let me know if we need any more data points.

22

Your activity has a 24-hour StartToClose timeout. So if its process fails during its execution (or it cannot report its completion to the service due to any reason) it will be retried only after 24 hours. What is the reason for using such a long timeout for a short activity?

See The 4 types of activity timeouts for more info.

2 Likes
23

No specific reason as such. It was an experimental run. So we used large values, to begin with. Not seeing the issue after setting the right values.

Thanks for sharing this. This was very helpful in making the understanding of timeouts better.