Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt

Use this file to discover all available pages before exploring further.

This page covers the common errors you might encounter when sending requests to the APIs.

​
Journey completes immediately with no module results

This is usually caused by the selected modules in the Journey builder not having the needed credentials. In this case, the journey completes with a 201 status code but returns no module results. To confirm this, send a POST request to the /journey/state/fetch endpoint. You will receive a response showing the GET_CREDENTIALS_ERROR code. To resolve this, contact your GBG GO account manager to update the credentials for your modules.
When you call the /journey/state/fetch endpoint and receive a “COMPLETED” status (rather than a credentials error), this means that the journey has been successfully finished and no further action is required.

​
Immediate logout after authentication

If you are a new user who attempts to log in to GBG GO with valid credentials but is immediately logged out, this might be because your organization hasn’t been created in the system yet. The account exists, but without an associated organization, the system cannot direct you to your dashboard and automatically logs you out. To resolve this, contact your GBG GO account manager for help troubleshooting the issue.