Host IDs

Overview

The Functions Host uses a Host ID to uniquely identify a particular Function App. By default, the ID is auto-generated from the Function App name.

Host ID Collisions

If you have multiple Function Apps sharing a single storage account and they're each using the same Host ID, that will result in a collision. The HostID is used by the platform to store per-app correlated control/tracking information in the storage account. When multiple apps are using the same HostID (a collision), this can result incorrect behaviors. For example, some triggers like TimerTrigger/BlobTrigger store tracking info by HostID and can behave incorrectly when multiple apps use the same ID.

Options for addressing this error:

1. Point your app at a different storage account.
2. Rename your app so something less than 32 characters in length. This will change the computed HostID for the app and remove the collision.
3. Add an app setting AzureFunctionsWebHost:hostId to your app to override the computed HostID with the one you specify.
4. Disable this error via the FUNCTIONS_HOSTID_CHECK_LEVEL. Only do this if none of the options above are possible for you.

Keep in mind that pointing an existing app to a new storage account, or changing the HostID or name of the function app can impact function processing. For example, BlobTrigger tracks whether it's processed individual blobs by writing "receipts" under a HostID path in storage. If the HostID changes or you point to a new storage account, that can lead to blobs being reprocessed. For a new app that hasn't processed work yet, this won't be a problem.