We checked your "facility-manager" service and confirmed the initialization failure you encountered was a transient platform-side connectivity issue, not caused by your code or configuration. Your service currently shows a successful deployment and is running normally. There is no ongoing incident affecting your project, and no mitigation is needed on your side. If you see this error recur, a simple redeploy from the dashboard should resolve it.

ror:**

'/orchestrator.BuildService/StartSnapshotAndBuild UNKNOWN: failed to get temporal client: client.Dial: failed reaching server: connection error: desc = "transport: Error while dialing: dial tcp 10.10.10.50:7233: connect: cannot assign requested address"'

Issue Description:

I'm experiencing a deployment failure during the snapshot and build initialization phase. The error indicates that the system cannot reach the Temporal server at 10.10.10.50:7233.

Error Analysis:

• Service: orchestrator.BuildService/StartSnapshotAndBuild
• - Root Cause: Temporal client connection failure
• - Server Address: 10.10.10.50:7233
• - Error Type: Connection refused - "cannot assign requested address"

Impact:

• Deployment cannot proceed
• - Build pipeline blocked
• - Unable to deploy new versions

Troubleshooting Attempted:

• Verified network connectivity
• - Checked service availability
• - Confirmed configuration settings

Request:

Please investigate why the Temporal server connection is failing and provide guidance on resolving this connectivity issue. This appears to be a critical blocker for our deployment pipeline.

Seeing this with our application as well

We identified and resolved a build infrastructure issue that was causing initialization failures. Your service's latest deployment already completed successfully. If you encounter any further issues, please let us know.