Customer connection status evidence

Make connection status distinguish configured from working

Review connection messaging in your product without treating a badge as proof that an external service is reachable or synchronized.

  • ✓Badges contradict detailed guidance
  • ✓Canceled recovery looks successful
  • ✓Unknown checks appear healthy

Connection-screen reports without provider assumptions

Status meanings made explicit

Distinguish saved configuration, authorization, and a recent check through owner-approved wording.

Recovery-state consistency

Show the badge and detail panel together after a canceled reconnect attempt.

Provider claims kept separate

Keep visible settings feedback distinct from network and synchronization checks outside Retick.

Review status inside your customer's product

This workflow examines an integration connection screen in your customer's application, not a promise that Retick connects to the providers shown there. Use a safe test connection with configured, expired, and disconnected display states. Capture the connection name, status label, last-check text, and available action. Record what each state is intended to mean. A green Connected badge may indicate saved configuration rather than a successful recent request, and the review should preserve that distinction.

Show status changing during recovery

Record opening an expired connection, starting the supported reconnect path, and returning to the status page with a controlled failure or cancellation. Keep credentials and authorization material entirely outside the capture. An example issue is Canceled reconnect restores the green badge while the detail panel still says Authorization expired. Show both indicators together. Do not claim that a provider accepted a token or that synchronization resumed merely because one label changed.

Define consistent status communication

Capture the browser interface with Retick or upload supported screenshots and recordings. Review AI candidate issues, edit inferred provider behavior, reject claims about successful connectivity, and annotate the conflicting labels. Example acceptance criteria: canceling reconnect leaves a consistent product-approved status; the primary action matches that state; and last-check wording distinguishes an unknown result from a confirmed successful check. Have the integration owner approve these meanings before the issue uses terms such as healthy, authorized, or synchronized.

Follow up with restricted and missing states

After implementation, manually repeat with a user who cannot manage connections, a connection without a previous check, and a deliberately disconnected test account. Inspect long provider labels and failure guidance on a narrow screen. Verify actual authorization, network requests, and data synchronization with your own integration tests and provider tools. Retick does not inspect hidden tokens, connect arbitrary services, or verify backend health. Remove secrets before capture rather than expecting automatic redaction.

Download the reviewed findings for a manual file handoff, or export selected issues from the individual media item to a connected Trello board and list. That selected issue export is separate from the customer's integration being reviewed. Include the canceled reconnect sequence and approved status definitions so engineering can reproduce the UI inconsistency without assuming connectivity was tested.

Review a connection status contradiction

Capture the recovery path and the labels that disagree afterward.