Skip to main content

Support

Anyone using AlphaAgent (Organisation administrators, deployers, Studio users and integrators) writes to hello@prometheusrl.com; there is no other support channel, and with the details below the first reply can go straight to the cause.

Steps​

  1. Check Troubleshooting and FAQ for the exact message you see; most refusals name their own remedy. For a failed deployment job, read the failure card in the deployment's Jobs view first: Who acts says whether the fix is in your account, and What to check says what it is. For a Studio banner, read Banners you may see.
  2. Gather the identifiers from the table below for the surface you were on.
  3. Copy the exact text of the message or banner, or the failure code from Technical details.
  4. Note when it happened, with the time zone (the Organisations console's Audit view shows times in UTC).
  5. Email hello@prometheusrl.com with the identifiers, the text, the time and what you expected to happen. Attach screenshots or a downloaded step log if you have them.

What to include​

ItemWhere to find it
Your Organisationthe hostname of your Organisations console (for example org.example.com) and the organisation name shown in the AlphaAgent Console under Organization & profile
Deployment IDthe sticky header of the deployment in the Organisations console (Fleet → the deployment), beside Name, Account, Version and Status
Diagnostic ID (the job id)the failure card on the deployment's Jobs view, with a Copy button; the Job column of the Jobs list shows the same id
Failure codeTechnical details on the failure card, for example access_denied_missing_action
Step logDownload full log on the failed step in the step timeline (the file is named <jobId>-<stepId>.log)
Timestampswhen it started and when it failed, in UTC or with your time zone
Studio versionthe footer of Studio's left sidebar ("Studio" followed by the version), or Profile → Deployment → Version; also the Version cell in the deployment's header in the Organisations console
Licence idthe deployment's Overview in the Organisations console (Licence id); it starts with aalk_ and is safe to share
Request id (API calls)the request_id field in the error body, echoed from the X-Request-Id header you sent or minted by the API
Pull or share requestthe item name, the Resource Store and the reason shown under My Pulls or the Shared to strip
The exact textthe banner, error or refusal, quoted as shown
What you expectedone sentence
Never share secrets

Do not include the License Token (aalk_<id>.***), an API key or its key external id, the Entra client secret, connector credentials, AWS credentials or any customer data. The identifiers above are enough to find the deployment, the job and the request.

What you should see​

A reply from the AlphaAgent team to the address you wrote from. If the failure card said AlphaAgent under Who acts, the Diagnostic ID lets the team open the job directly.

Notes​

  • If you cannot reach the Organisations console to read a Deployment ID or Diagnostic ID, send what you have: the console hostname, the deployment's name and app domain, and the time.
  • The documentation carries no release notes; the version you are running is shown in the product as described above.