Unable to Retrieve User Creation Date or "Member since" via CloudHealth GraphQL API
search cancel

Unable to Retrieve User Creation Date or "Member since" via CloudHealth GraphQL API

book

Article ID: 434801

calendar_today

Updated On:

Products

CloudHealth

Issue/Introduction

Symptom: Users attempting to automate onboarding workflows or reporting via the CloudHealth GraphQL API are unable to find fields for "Member since" or a "Created at" timestamp. While lastSignIn and lastActivity are available, the account creation date visible in the UI is missing from the API schema.

Problem: Customers may attempt to use the numeric portion of the CloudHealth Resource Name (CRN) as a proxy for chronological ordering (assuming higher numbers are newer users). However, the CRN is a globally unique identifier and is not designed to be sequential.

Cause

The current GraphQL API schema for the User node does not expose the createdAt attribute. This is a known product limitation. Furthermore, CRNs contain multiple metadata components, including customer IDs, making them unsuitable for inferring the order of creation.

Resolution

Currently, the "Member since" attribute can only be retrieved via the CloudHealth UI or manual export.

Option 1: Manual Export via UI

  1. Navigate to Setup > Admin > Users.
  2. Review the Member since column for the desired users.
  3. Click Export to CSV to download a full list containing creation dates Details For Users.

Option 2: Automation Workaround

For automation tasks (such as sending "Welcome" emails to new users), it is recommended to maintain a local state:

  1. Periodically query the GraphQL API for the list of all users.
  2. Store the retrieved User IDs (CRNs) in a local database or file.
  3. Compare subsequent API results against the local record.
  4. Any newly discovered ID that was not previously in the local record can be treated as a "new" user.

Note: Do not rely on the last digits of the CRN (e.g., crn:12345:user/384062) to determine which user is "newer," as these IDs are not guaranteed to be strictly increasing or chronological.