---
sidebar_label: Troubleshooting
doc_id: 7c520105-e291-4e4b-81b2-f6260b0e8237
description: >-
  Guide for resolving common issues with service instances, including failures
  and deletion problems.
keywords:
  - troubleshooting
  - service failure
  - service instance
---

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Troubleshooting

If you've encountered issues, use this page to identify and solve them.

---

## My service instance failed

Your service displays a `failed` status when attempting a `create`, `update`, or `delete` action.

Service instances are intentionally moved to a `failed` state to prevent broken services from continuing to run. This allows you time to review the failure, decide whether repairs are needed, or determine if the service can be safely reactivated.

### Failure during `update` or `delete` actions

If this error occurs and the service can be safely reactivated.

**Fix:**

> **Note:** You need an [ops role](/docs/authorization/roles) to perform the following actions.

1. Make a [PATCH request to update the service](/docs/api/service-update):

    ```bash
    np service patch \
      --id :id \
      --body '{
        "status": "active"
        // Update or re-declare any other values, if needed
      }'
    ```

2. Retry updating or deleting your service instance from the dashboard.

### Failure during `create` action

  This usually happens when the initial service configuration is incorrect.

  **Fix:**

  > **Note:** You need an [ops role](/docs/authorization/roles) to perform the following actions.

  1. **Check the logs** for any misconfigurations.  
  2. **Delete** the failed service instance from the dashboard.  
  3. **Create** a new service instance with corrected values.