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

# Troubleshooting

> The full-replace PUT trap, listing gotchas, and per-connector-type quirks for Automated Project Creation.

## Enabling, disabling, or editing silently doesn't stick

There is no dedicated enable/disable or partial-update endpoint for APC. `GET .../running` and `GET .../status` are read-only state checks — they can't be used to change anything.

The **only** write path for any change, including just flipping `active`, is:

```bash theme={null}
PUT /api2/v3/automatedProjects/{settingsId}
```

This is a **full replace** — it requires `frequency`, `id`, `monitoredFolders`, and `name` in the body regardless of what you're actually changing.

<Warning>Sending a body with only the field you're changing (e.g. just `{"active": true}`) can be accepted by the API without an error, but doesn't actually persist the change — a follow-up `GET` will show the setting reverted to its previous state. The response echoing back your intended value is **not** proof the change was saved.</Warning>

To make any change safely:

1. `GET /api2/v3/automatedProjects/{settingsId}` first — **not** the `GET /api2/v1/automatedProjects` list result, which is a flatter shape (`connectorId`/`connectorName` instead of nested `monitoredFolders`) and is missing fields the `v3` `PUT` requires.
2. Take that full object, change only the field(s) you actually want to change, and send the **complete** object back.
3. `GET` the same `settingsId` again afterward and confirm the field actually changed before considering the update successful.

## Listing has no owner/creator field

Neither the list nor the single-get response for an APC setting exposes who created it. There's no way to filter "my APC settings" — either server-side or by post-processing the response, since the field simply isn't there. If you need to narrow a large list down, filter by connector, by active/inactive state, or by name instead.

## Listing is paginated

`GET /api2/v1/automatedProjects` returns at most 50 results per call (`pageSize`, default and max 50; `pageNumber`, 0-indexed). Check `totalElements`/`totalPages` on the first response and keep paging until you've collected everything — reporting the first page's contents as "the full list" is wrong the moment your organization has more than 50 APC settings.

## `PHRASE` connectors are a valid, real connector type

`PHRASE` (the connector that connects TMS to Phrase Strings) is a documented `ConnectorType` enum value, same as `BOX`, `GIT`, `CONTENTFUL`, `MARKETO`, or `OPTIMIZELY` — it's a legitimate choice for an APC's underlying connector. If browsing its folders behaves differently than a filesystem-backed connector (see [Creating an APC](/en/guides/managing-automated-project-creation/creating-an-apc)), that's a property of that connector type, not a sign it doesn't exist or isn't supported.

## Deletion

`DELETE /api2/v1/automatedProjects/{settingsId}` deletes one setting; `DELETE /api2/v1/automatedProjects/batch` deletes several by id in a single call. Both are permanent — confirm the exact setting(s) before calling either.