> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/port-calls/port-call-drawer/view-port-log-on-port-calls/stoppages.md).

# Stoppages

In the port log tab there will be an overview of stoppages registered for both cargo ports, and for the port call. 

A list of all cargo ports connected to the port call will be displayed in the form of collapsible panels.

![Cargo Port collapsible panels](https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/yDKKilwibkfSRR2lOpXS/Screenshot%202021-09-02%20at%2008.57.27.png)

When opening a cargo port panel, a list of stoppages will be presented. The stoppages are editable if the cargo port does NOT have a laytime calculation connected. 

![The list of stoppages on a cargo port](https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/YNA3eNKntds6Z2zmA0uk/Screenshot%202021-09-02%20at%2009.10.32.png)

It is possible to create new stoppages for a cargo port, by clicking the + sign in the top right corner of the cargo port panel. It is the same fields for creating and editing a stoppage.

![Fields that are available on a stoppage](https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/EiqWZmmfhR7s1hol74Pq/Screenshot%202021-09-02%20at%2009.14.22.png)

Underneath all the cargo ports, a list of all stoppages related to the port call will be displayed. Stoppages that are related to the connected cargo ports will be marked with the commodity name as well.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/port-calls/port-call-drawer/view-port-log-on-port-calls/stoppages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.