From e67d28787ab92188583353fa11563a6a0c75d31f Mon Sep 17 00:00:00 2001 From: sankari gopalakrishnan Date: Wed, 28 Aug 2024 11:49:23 +0200 Subject: [PATCH] [Wf-Diagnostics] Adding a short description to timeouts (#191) --- src/docs/08-workflow-troubleshooting/01-timeouts.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/docs/08-workflow-troubleshooting/01-timeouts.md b/src/docs/08-workflow-troubleshooting/01-timeouts.md index 545e4964f..cd8cf9c5f 100644 --- a/src/docs/08-workflow-troubleshooting/01-timeouts.md +++ b/src/docs/08-workflow-troubleshooting/01-timeouts.md @@ -6,6 +6,8 @@ permalink: /docs/workflow-troubleshooting/timeouts # Timeouts +A workflow could fail if an activity times out and will timeout when the entire workflow execution times out. Workflows or activities time out when their time to execute or time to start has been longer than their configured timeout. Some of the common causes for timeouts have been listed here. + ## Missing Pollers Cadence workers are part of the service that hosts and executes the workflow. They are of two types: activity worker and workflow worker. Each of these workers are responsible for having pollers which are go-routines that poll for activity tasks and decision tasks respectively from the Cadence server. Without pollers, the workflow cannot proceed with the execution.