A complete guide to multiple rocks showing as the same rock.

Multiple Rocks Showing as the Same Rock

Occasionally, customers report that two or more rocks in their workspace appear identical in the dashboard, sharing the same name, thumbnail, or both. This article explains the underlying causes and how to resolve them.

Confirm whether the issue is rendering or data

Before troubleshooting, determine which type of duplication you are seeing.

Rendering duplication

Two distinct rocks (different IDs) display the same thumbnail or name in the dashboard, but the API returns correct distinct data for each.

Data duplication

Two rocks share the same internal ID, or API responses for different rocks return identical payloads.

Run the following for each affected rock:

curl https://api.petrock.cloud/v1/rocks/{rock_id} \
  -H "Authorization: Bearer $PETROCK_API_TOKEN"

Compare the id fields in the responses. Distinct IDs with identical other fields indicate rendering duplication. Identical id fields indicate data duplication, which is rare and should be reported.

Cause 1: Thumbnail cache collision

The dashboard generates thumbnail URLs using a hash of the rock name plus a salt. If two rocks share an identical name (which should be prevented by the uniqueness constraint, but can happen across environments or after a rename), they may render the same cached thumbnail.

Fix:

  1. Open each affected rock's detail page.
  2. Click the overflow menu and select Regenerate Thumbnail.
  3. Hard refresh the dashboard.

Cause 2: List view group-by misconfiguration

The rock list view supports grouping by tag, region, or environment. If grouping is set to a field that all your rocks share, the list may collapse rows in a way that makes them appear merged.

Fix:

  1. In the rock list, click Group by.
  2. Select None or a more granular field like ID.
  3. Verify each rock now displays as a distinct row.

Cause 3: UUID collision (extremely rare)

Rock IDs are generated using UUID v4. The probability of collision is statistically negligible, but in the documented incident PR-2143 (October 2024), a deployment regression caused 14 IDs to be generated from a non-random source over a 7-minute window. If you suspect this:

  1. Note the affected rock IDs.
  2. Check the provisioning timestamps in the audit log.
  3. Contact support with the IDs and timestamps.

Note: Affected rocks from PR-2143 were automatically reassigned new IDs on November 4, 2024. If your rocks were provisioned after that date, this cause is not applicable.

Cause 4: Browser extension interference

Some accessibility and ad-blocking extensions modify the DOM in ways that can collapse list items they consider visually similar. To rule this out:

  1. Open the dashboard in a private/incognito window with extensions disabled.
  2. If the duplication does not appear, identify the extension by toggling them on one at a time.

When to contact support

Contact support if:

  • Two rocks share the same id field in API responses
  • Regenerating thumbnails does not separate visually identical entries
  • The audit log shows two rock.provisioned events with identical IDs

Include the rock IDs and a screenshot in your support request.