Skip to content
This repository was archived by the owner on Dec 29, 2025. It is now read-only.

Commit f63d2a2

Browse files
CopilotJohannesRudolph
authored andcommitted
Add Building Block timeout detection and warning message documentation
Co-authored-by: JohannesRudolph <[email protected]>
1 parent ef1bf12 commit f63d2a2

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

docs/concepts/building-block.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,30 @@ This approach is not limited to AWS. Many OpenTofu providers support authenticat
142142

143143
meshStack simplifies credential management by offering preconfigured inputs for common platforms. When creating an OpenTofu building block, you can use the "Generate Input" menu to automatically add the necessary credential inputs for AWS, Azure, or GCP. For example, selecting "Generate AWS auth inputs" will create the required AWS credential inputs. You can then assign static values or allow users to provide them at runtime.
144144

145+
## Monitoring and Troubleshooting
146+
147+
### Building Block Execution Monitoring
148+
149+
meshStack provides visibility into building block execution through run details and status information. Each building block instance shows its current state and execution history, helping you track provisioning progress and identify any issues.
150+
151+
### Timeout Detection and Warning Messages
152+
153+
Building blocks include enhanced timeout detection that provides better visibility into execution issues. When a building block run experiences timeouts, warning messages are displayed in the building block run details to help you understand what happened and why.
154+
155+
**Building Block Timeout and Retry Behavior:**
156+
157+
By default, building block runs have a timeout of 3 hours. When a timeout occurs, the system automatically retries the run indefinitely until one of the following happens:
158+
159+
- **The run reaches a final state** (succeeded or failed)
160+
- **The run is manually aborted** by an operator
161+
- **A new run is triggered** for the same building block
162+
163+
This automatic retry mechanism helps resolve temporary issues that may cause timeouts, such as network connectivity problems or temporary platform unavailability. When the circumstances change (like a network issue being resolved), the retried run can complete successfully.
164+
165+
**Important retry behavior:** If a new run is triggered while an existing run is still being retried after timeouts, the system will stop retrying the old run and execute the new one instead. This ensures you always get the most current configuration applied.
166+
167+
Timeout warnings in the building block run details provide transparency into execution performance and help you understand when retries are occurring.
168+
145169
## Related Resources
146170

147171
### Concepts

0 commit comments

Comments
 (0)