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

​
Empty collection of tasks when sending a request to retrieve tasks

This is usually caused by the selected modules in the journey builder not having the needed credentials. In this case, you encounter a 201 status code that returns an empty collection of tasks even when you have modules in the journey builder. The response looks like this:

{
    "status": "Completed",
    "instanceId": "Qs7Zj2p4LMWT3V8Ndu9k6BRa",
    "tasks": []
}

To confirm this, send a POST request to the /journey/state/fetch endpoint. You will receive a response showing the GET_CREDENTIALS_ERRORcode.

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. All tasks associated with this journey instance have been completed, 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.