> ## Documentation Index
> Fetch the complete documentation index at: https://ago.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Known Problems

> See recurring integration failures that you can fix yourself, and mark them as resolved

The Known Problems page lists failures that keep happening in your workspace and that an admin can usually fix, for example credentials refused by your ticketing system, a knowledge source that will never sync, or a connection that needs reconnecting.

To open it, go to **Settings** > **Known Problems**. You need the **Admin (staff)** status, see [User Management](https://ago.mintlify.site/features/admin-user-management.md#roles).

## What the page shows

Each problem shows:

* What failed and what to do about it, with a link to the setting to fix
* How many times it happened, and when it was first and last seen. Repeats within the same minute count once.
* The last occurrence, for example the ticket, conversation, field or source concerned
* Whether it is **Open** or **Resolved**

Repeats of the same problem, with the same cause and on the same item (a field, a source, a trigger...), are grouped into one entry. Open problems are listed first, then resolved ones, up to the 200 most recent entries.

## Mark a problem as resolved

After you fix the cause, click **Mark as resolved**. If the problem happens again, a new entry opens and its count starts from one, so you can tell whether your fix worked.

## Problems AGO reports

### Ticketing

| Problem | What to do |
| - | - |
| **Ticket creation failed** in your ticketing system, such as Zendesk, HubSpot, Help Scout or Freshdesk. The user saw an error. | If the system refused AGO's credentials, update them in the ticketing system configuration. If it refused the ticket, check the fields it requires. Contact AGO support if the cause is unexpected. |
| **Automatic ticket not created** for an inactive conversation | Same causes as above. If the conversation's user is not allowed to create tickets, give them an active account with the same email address in your ticketing system and access to the ticket form, or ask AGO support to allow all users to create tickets. |
| **Ticket field value ignored**: the ticket was created without one value | The field is unknown, a checkbox received something other than true or false, or the value is not one of the field's options. Add the option to the field, or fix the form, widget or integration that sends the value. |
| **HubSpot ticket attachments not delivered** | Add the `files.write` scope to the HubSpot service key. If HubSpot refused the file, check the file type and size limits of your HubSpot account. The ticket itself is created. |

### Knowledge and integrations

| Problem | What to do |
| - | - |
| **Knowledge source schedule incomplete**: automatic sync is on but will never run | Open the source and complete its sync schedule. |
| **URL blocked**: AGO did not call a URL set in an API data source, a ticket or conversation trigger webhook, or a form collector | If the URL points to a private or internal address, use a public one: AGO never calls private addresses. If it is invalid, correct it and check that the values it uses are always filled in. If its host name can't be found, check its spelling and that the service is reachable from the internet. |
| **Connection needs reconnecting**: a Notion or SharePoint connection can no longer renew its access | Reconnect the Notion or SharePoint connection. Its sources stop syncing until you do. |

## Related

* [HubSpot](https://ago.mintlify.site/data-connector/hubspot-integration.md): HubSpot ticketing configuration
* [Ticketing](https://ago.mintlify.site/features/ticketing.md): ticketing overview
* [Knowledge Source Management](https://ago.mintlify.site/features/knowledge-source-management.md): sync schedules


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.