Add Temporl worker connection failure#56
Merged
tonymeehan merged 1 commit intoprequel-dev:mainfrom Jun 5, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
👋 Hey team,
Submitting my solution for the Temporal worker connectivity failure detection bounty. This implementation provides a minimal and reproducible test setup, along with a CRE-format rule to detect a worker connection failure when the Temporal server is unreachable.
📋 Details
/claim #39
Reproducible test setup (Maintainers invited): Temporl
Live CRE link: CRE Playground
Log file:
worker.log🎥 Video Demonstration
A complete test demo showing worker failing to connect while server is down and CRE rule triggering:
TemporalWorker.RefusedConnection.mp4Screen.Recording.2025-06-05.154406.mp4
🚨 What This Detects
This rule captures a critical failure mode in self-hosted Temporal environments:
🧪 Reproduction Process
Run the following steps to simulate the issue: