> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/documentation/troubleshooting/ellucian-colleague-timeout-errors.md).

# Troubleshooting Ellucian/Colleague Timeout Errors

This article covers how to handle 30,000ms timeout errors between Unimarket and Ellucian Colleague, effectively.

## Integration Architecture Overview

These errors typically occur when the **Ethos API** or the underlying **Colleague** database is under heavy load or experiencing network latency, causing the Unimarket request to be terminated by the server.

If you receive an error email containing one of the following messages, it indicates that the communication between Unimarket and Ellucian Colleague has timed out (exceeding the 30,000ms limit).

### Error Samples

* `Get PO call failed for PO PXXXXXX. Error message is Request ran for longer than 30000ms...`
* `Get Persons call failed for PO PXXXXXX. Error message is Request ran for longer than 30000ms...`

## Immediate Action Steps for Users

Before reaching out to the Unimarket Support team, follow these steps to determine if the issue is a temporary cloud service interruption.

1. **Check Service Status:** Visit the [Ellucian Cloud Status Page](https://status.elluciancloud.com/).
   * **If an issue is reported:** Do **not** attempt to resend the PO. Wait until the status page indicates the service is fully operational.
   * **If no issue is reported:** Proceed to Step 2.
2. **Verify Colleague Entry:** Wait **30 minutes**. Log into Colleague and check if the PO was actually created, despite the timeout error.
3. **Manual Resend:** If the PO is missing from Colleague after 30 minutes, go to the Unimarket portal and **Resend** the PO.
4. **Escalate:** If the PO still fails to appear in Colleague after a manual resend, contact **Unimarket Support**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.unimarket.com/documentation/troubleshooting/ellucian-colleague-timeout-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.