---
title: "Instances Without Application or Service Name After Deleting an Artifact"
slug: "challenges-dealing-with-user-access-policies-and-deleted-biztalk-artifacts"
updated: 2026-11-05T06:45:38Z
published: 2026-11-05T06:45:38Z
canonical: "docs.biztalk360.com/challenges-dealing-with-user-access-policies-and-deleted-biztalk-artifacts"
---

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

# Instances Without Application or Service Name After Deleting an Artifact

## Scenario

Consider the following scenario:

A message is received through a Receive Port named **Receive.Simple.Messaging.File**. The message is suspended because no matching subscriptions are found. When you query for the instance, the result initially appears as shown below:

![image.png](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image%28232%29.png)

Now, suppose someone deletes the **Receive.Simple.Messaging.File** Receive Port. The instance will continue to exist in the system because it is a historical record. However, the reference to the deleted Receive Port is no longer available.

When you query for the same instance again, the result will appear similar to the following:

![image.png](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image%28233%29.png)

As you can see, the **Service Name** is no longer available, and the corresponding **Application Name** is also missing.

## Challenge

If the user is accessing BizTalk360 as a **Super User**, the behavior will be similar to what is observed in the BizTalk Server Administration Console. The instance can still be displayed even though the associated Receive Port has been deleted.

![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-GKYOXWMM.png)

However, the behavior is different for users with **limited access**.

For example, assume a user has permission to access only the **Simple.Messaging** application. BizTalk360 applies user access policies at the **application level**.

Since the Receive Port was deleted, the instance no longer contains a reference to the application. As a result, BizTalk360 cannot determine whether the instance belongs to an application that the user is authorized to access.

Therefore, the instance **will not be displayed** in the query results for the limited-access user.

## Explanation

This is an uncommon scenario and is primarily caused by the removal of the application artifact associated with the historical instance.

The BizTalk Server Administration Console can continue to display the historical instance even after the associated Receive Port has been deleted. However, BizTalk360 must apply its application-level access restrictions before displaying the instance to a limited-access user.

When the application reference is no longer available, BizTalk360 cannot validate the user's access permissions for that instance. As a result, the instance is excluded from the query results.

## Recommendation

This is not a typical scenario and can be considered a limitation of how historical instances are handled when their associated artifacts are deleted.

As a best practice, avoid deleting BizTalk artifacts that are still referenced by historical instances unless there is a specific requirement to do so.

If an artifact needs to be removed, consider the impact on historical instance information and on users who have restricted application-level access in BizTalk360.