Skip to main content

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 to perform the following actions.

  1. Make a PATCH request to update the service:

    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 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.

You won’t be able to delete an application if it still owns any services or links. You’ll need to transfer ownership first.

There are a few ways to check what services or links the application owns:

  • From the UI:
    Go to Development > Services and select the Owned by this application tab.

  • From the CLI:
    Use the service list or link list commands, providing the application's entity_nrn as a query parameter.

    Tip: For services, make sure the nrn (source) matches the entity_nrn.

    np service list 
      --nrn organization=1:account=1:namespace=1:application=1  
      --entity_nrn organization=1:account=1:namespace=1:application=1

    These commands will show you what the application currently owns and is blocking its deletion.

  • From the API:
    You can also make a service list or link list request directly to the API, using the application's entity_nrn as a query parameter. The same logic used in the CLI examples applies here as well.

2. Change the owner​

Once you’ve identified the service or link, you’ll need to update its owner by changing the entity_nrn to a different application. Use a PATCH request to services or links for that, like this:

np service patch \
  --id <SERVICE_ID> \  
  --body '{
    "entity_nrn": "organization=1:account=1:namespace=1:application=2"
  }'

Just swap in the right IDs and target NRNs for your case.

3. Update the linkable_to property​

After you transfer ownership, you might also want to update the service’s linkable_to property, so it reflects the new relationships between applications.

Need more info?

Check out the services docs.

Still need help?

If none of the solutions resolve the issue, reach out to us for support.