hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether the request to set the adapter's name has succeeded. Emitted when the request succeeds or fails. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether the request to set the adapter's scan mode has succeeded. Emitted when the request succeeds or fails. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records time spent in milliseconds to establish a Bluetooth service connection successfully. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records the result of {Operation}. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether the request to start advertising has succeeded. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether BLE scanning has been initiated successfully. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether the request to stop advertising has succeeded. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether BLE scanning has been stopped successfully. julietlevesque@chromium.org nearby-share-chromeos-eng@google.com Records the number of parsing attempts it takes the stream parser to check byte by byte if the data it received forms a valid StreamBody proto. Emitted every time we get a receive-express HTTP response from the Instant Messaging API. cclem@chromium.org nearby-share-chromeos-eng@google.com Records whether the cache was used to satisfy the GetIceServers request. Emitted when GetIceServers is called. cclem@chromium.org nearby-share-chromeos-eng@google.com Records the HTTP response code or net error code of the GetIceServers API call to the Tachyon server. Emitted only on failure or timeout. cclem@chromium.org nearby-share-chromeos-eng@google.com Records whether the Tachyon OAuth token was successfully fetched. Emitted when the token fetcher request returns. cclem@chromium.org nearby-share-chromeos-eng@google.com Records the result of the GetIceServers API call to the Tachyon server. Emitted when the http response is received or when the call times out. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether or not the user was able to fetch the OAuth token necessary to {Direction} the Instant Messaging API. Emitted at the conclusion of the token request, which is attempted right before making HTTPS requests to the Instant Messaging API. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether an HTTPS call to {Direction} the Instant Messaging API succeeds or fails. Emitted when the HTTPS call succeeds or fails. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records the network error code or HTTPS response code from a failed HTTPS call to {Direction} the Instant Messaging API. Emitted when the HTTPS call fails. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records why the Sharing utility process, which hosts Nearby Connections, was shut down: for an expected reason (i.e., shut down request from a client), or another unexpected reason (e.g., a crash). hansenmichael@google.com nearby-share-chromeos-eng@google.com Records which Mojo dependency of the Sharing utility process disconnected from the browser process. This will not necessarily line up with the counts in the Mojo disconnect bucket of Nearby.Connections.UtilityProcessShutdownReason which tracks disconnects on the utility process side. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records the result of trying to connect to another device's TCP server socket. Emitted after a cross-device connection attempts to be established over TCP sockets. Note: One device listens for incoming connections while the other device tries to connect. This metric is logged by the connecting device. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records the result of listening for and accepting incoming TCP socket connections. Emitted after a cross-device connection attempts to be established over TCP sockets. Note: One device listens for incoming connections while the other device tries to connect. This metric is logged by the listening device. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records the result of a TCP server socket accepting incoming connections. This is a lower-level metric that tracks the result code from the TCP server socket accept call made in the networking layer. Emitted after a cross-device connection attempts to be established over TCP sockets. Note: Only one device opens a server socket, which the other device attempts to connect to. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records the time it takes to successfully connect to another device's TCP server socket. Emitted after a cross-device connection is established over TCP sockets. Not emitted on failure. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records success or failure when {Operation} of a {Medium} socket. Emitted during cross-device data transfers. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the total number of attempts of downloading the remote devices' SharedCredentials from the Nearby Presence Web Server needed for a successful download. Emitted on success to reflect the final count of attempts required to download credentials from the server. No metric is emitted on failure. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the failure reason of a single attempt to download the remote devices' SharedCredentials from the Nearby Presence Web Server. Emitted after every unsuccessful attempt to download credentials from the server. No metric is emitted on success. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the overall success or failure of downloading the remote devices' SharedCredentials from the Nearby Presence Web Server. Emitted after all retries to download from the server have been completed, to reflect the final result of downloading credentials from the server. julietlevesque@google.com chromeos-cross-device-eng@google.com Records time spent in milliseconds to receive a response from the Nearby Presence Web Server after a download request for remote devices' credentials. Emitted after a successful response from the server. Note that there is a timeout at 5 seconds. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the result (success or failure reason) of the first time server registration flow for Nearby Presence. The first time server registration flow occurs only once per user per device. Emitted on failure or success of the overall flow. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the total number of attempts of registering the local device with the Nearby Presence Web Server during the first time registration flow. The first time server registration flow occurs only once per user per device. Emitted on success to reflect the final count of attempts required to register with the server. No metric is emitted on failure. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the failure reason of a single attempt to register the local device with the Nearby Presence Web Server. The first time server registration flow occurs only once per user per device. Emitted after every unsuccessful attempt to register with the server. No metric is emitted on success. julietlevesque@google.com chromeos-cross-device-eng@google.com Records time spent in milliseconds to receive a response from the Nearby Presence Web Server after an upload request during first time server registration. Emitted after a successful response from the server. Note that there is a timeout at 5 seconds. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the total number of attempts of uploading the local device's SharedCredentials to the Nearby Presence Web Server needed for a successful upload. Emitted on success to reflect the final count of attempts required to upload credentials to the server. No metric is emitted on failure. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the failure reason of a single attempt to upload the local device's SharedCredentials to the Nearby Presence Web Server. Emitted after every unsuccessful attempt to upload credentials to the server. No metric is emitted on success. julietlevesque@google.com chromeos-cross-device-eng@google.com Records the overall success or failure of uploading the local device's SharedCredentials to the Nearby Presence Web Server. Emitted after all retries to upload to the server have been completed, to reflect the final result of uploading credentials to the server. julietlevesque@google.com chromeos-cross-device-eng@google.com Records time spent in milliseconds to receive a response from the Nearby Presence Web Server after an upload request for the local device's credentials. Emitted after a successful response from the server. Note that there is a timeout at 5 seconds. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records each step in the background scanning notification flow if Nearby Share onboarding is complete. Emitted after the notification that a nearby device is trying to share is shown, and again when the user acts on the notification by clicking enable, dismiss or exit. Clicking enable puts the user in high-visibility mode. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records how long it takes for a user to act on a background scanning notification if Nearby Share onboarding is complete. Emitted after the user acts on the notification by clicking enable, dismiss or exit. hansenmichael@google.com nearby-share-chromeos-eng@google.com Logs an event when there were previously no devices nearby trying to share and now there are nearby devices trying to share. Emitted when the nearby devices trying to share changes from zero to greater than zero. A notification will not be shown on this event if the user dismissed the notification in the last 15 minutes.This metric is not emitted if the background scanning feature is disabled. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records for how long nearby devices were trying to share. Emitted after the number of devices trying to share goes from greater than zero to zero. This metric is not emitted if the background scanning feature is disabled. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records whether an attempt to start a background scanning session succeeded or failed. Emitted after the bluetooth adapter notifies whether starting the background scanning session was successfully started. This metric is not emitted if the background scanning feature is disabled. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records each step in the background scanning notification flow if Nearby Share onboarding is not complete. Emitted after the notification that a nearby device is trying to share is shown, and again when the user acts on the notification by clicking setup, dismiss or exit. Clicking setup initiates Nearby Share onboarding. hansenmichael@google.com nearby-share-chromeos-eng@google.com Records how long it takes for a user to act on a background scanning notification if Nearby Share onboarding is not complete. Emitted after the user acts on the notification by clicking setup, dismiss or exit. pushi@google.com nearby-share-chromeos-eng@google.com Records whether or not a Bluetooth MAC address was able to be fetched during the local device's private certificate creation. Emitted after private certificates attempt to be created, which typically occurs every three days if Nearby Share is enabled. This will only be emitted once if multiple certificates are created at a time, for example, when all certificates are created after onboarding. cclem@chromium.org nearby-share-chromeos-eng@google.com If the Nearby Share certificate manager successfully downloads public certificates, then record the total number of certificates downloaded across all pages. cclem@chromium.org nearby-share-chromeos-eng@google.com If the Nearby Share certificate manager fails to download public certificates, then record the page number of the page on which the failure occurred. cclem@chromium.org nearby-share-chromeos-eng@google.com Records the result of the async ListPublicCertificates API call to the Nearby Sharing server when the certificate manager periodically downloads public certificates. Recorded when the async callback is invoked or when the call times out. cclem@chromium.org nearby-share-chromeos-eng@google.com If the Nearby Share certificate manager successfully downloads public certificates, then record the number of pages downloaded by the RPC. cclem@chromium.org nearby-share-chromeos-eng@google.com Records whether the Nearby Share certificate manager successfully downloaded public certificates from the server and stored them in leveldb. cclem@chromium.org nearby-share-chromeos-eng@google.com Records the result of the async GetDecryptedPublicCertificate call in certificate manager. cclem@chromium.org nearby-share-chromeos-eng@google.com If the Nearby Share certificate storage successfully initializes the public certificate database, then record the number of attempts it took. cclem@chromium.org nearby-share-chromeos-eng@google.com For individual initialization attempts of the Nearby Share certificate storage public certificate database, record the init status returned by leveldb_proto. crisrael@google.com nearby-share-chromeos-eng@google.com Records the time necessary to successfully initialize the Nearby Share public certificates database. Emitted once after sign-in when the Nearby Share service starts. cclem@chromium.org nearby-share-chromeos-eng@google.com Record success rate of Nearby Share storage operation {Operation}. pushi@google.com nearby-share-chromeos-eng@google.com Records whether an attempt to establish a connection to a receiving device succeeded or failed; cancellations are ignored. Emitted after the user selects a device to send a payload to but before the payload begins its transfer. Because the sending device initiates the connection--via the Nearby Connections library--this metric is only emitted for outgoing transfers. crisrael@google.com nearby-share-chromeos-eng@google.com Records whether an attempt to establish a connection to a receiving device succeeded, failed, or was cancelled. Emitted after the user selects a device to send a payload to but before the payload begins its transfer. Because the sending device initiates the connection--via the Nearby Connections library--this metric is only emitted for outgoing transfers. pushi@google.com nearby-share-chromeos-eng@google.com Records the time necessary to successfully establish a connection to a receiving device. Emitted after the user selects a device to send a payload to but before the payload begins its transfer, and this is only emitted after a successful connection is established. Because the sending device initiates the connection--via the Nearby Connections library--this metric is only emitted for outgoing transfers. crisrael@google.com nearby-share-chromeos-eng@google.com Records whether or not we able to retrieve the profile user name--think email address--from the Chromebook's profile data. This value is sent to the Nearby Share server to allow sharing with other devices logged in with the same account. Emitted every time contacts are downloaded for use in Nearby Share. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. pushi@google.com nearby-share-chromeos-eng@google.com Contacts are downloaded in pages, i.e., multiple ListContactPeople RPC request/responses. Records the {Result}. Emitted every time contacts are downloaded for use in Nearby Share. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. crisrael@google.com nearby-share-chromeos-eng@google.com Records whether or not the full, possibly paginated contact download from the Nearby server was successful. Emitted every time contacts are downloaded for use in Nearby Share. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. pushi@google.com nearby-share-chromeos-eng@google.com Records the result of each ListContactPeople RPC call to the Nearby Share server. Emitted every time contacts are downloaded for use in Nearby Share. Due to pagination, this is emitted for every page of contacts downloaded. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. crisrael@google.com nearby-share-chromeos-eng@google.com Records the number of {Type} contacts downloaded from the Nearby server. Emitted every time contacts are downloaded for use in Nearby Share. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. pushi@google.com nearby-share-chromeos-eng@google.com Records the percentage of {Type} Emitted every time contacts are downloaded for use in Nearby Share. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. crisrael@google.com nearby-share-chromeos-eng@google.com Records the time spent {Result}. Emitted every time contacts are downloaded for use in Nearby Share. Because contacts are not stored locally, contacts are periodically downloaded for users with Nearby Share enabled and additionally whenever a user enters Nearby Share settings or participates in a sharing flow. pushi@google.com nearby-share-chromeos-eng@google.com Records the device type that the user {Direction}. Emitted when a transfer completes successfully, fails, or was aborted by the user, for example, by cancelling the transfer. crisrael@google.com nearby-share-chromeos-eng@google.com Records the delay between the start of the discovery session and {EndState}. pushi@google.com nearby-share-chromeos-eng@google.com Records the furthest state reached in a single Nearby Share discovery session. Emitted when the per-session discovery manager is destroyed. crisrael@google.com nearby-share-chromeos-eng@google.com Records whether or not the selected share target on the Nearby Share discovery page can be found in the per-session discovery manager's map of discovered share targets. Emitted when the user selects a share target from the discovery page and tries to proceed to the next step in the UI. pushi@google.com nearby-share-chromeos-eng@google.com Records the number of share targets {Variation} in a single discovery session. Emitted once during the discovery session. crisrael@google.com nearby-share-chromeos-eng@google.com Records the result of {Operation}. Emitted immediately after the operation is attempted for each discovery session. pushi@google.com nearby-share-chromeos-eng@google.com Records if the user has the Nearby Share feature enabled, and if not, records why the feature is not enabled. For example, the feature is not allowed by policy, or the user onboarded but later disabled the feature. Emitted on sign-in and whenever the feature state changes, for instance, from disabled to enabled. crisrael@google.com nearby-share-chromeos-eng@google.com Records the enabled/disabled state of Nearby Share. Emitted when the feature state changes from disabled to enabled or vice versa. This can happen after Nearby Share onboarding or when the user enables/disables the Nearby Share feature toggle in Settings. pushi@google.com nearby-share-chromeos-eng@google.com Records whether or not the device shared with is a known contact, i.e., contact-based sharing. Emitted when a transfer completes successfully, fails, or was aborted by the user, for example, by cancelling the transfer. brandosocarras@google.com nearby-share-chromeos-eng@google.com Records whether the share was a Self Share. Emitted when Self Share is enabled and a transfer completes successfully, fails, or was aborted by the user, for example, by cancelling the transfer. cclem@chromium.org nearby-share-chromeos-eng@google.com Records the result of the async UpdateDevice API call to the Nearby Sharing server when the device data updater makes a request. Recorded when the async callback is invoked or when the call times out. crisrael@google.com nearby-share-chromeos-eng@google.com Records the data-transfer medium that the Nearby Connections library successfully switches to during a Nearby Share transfer. Emitted when the Nearby Connections library notifies the client of a bandwidth upgrade. pushi@google.com nearby-share-chromeos-eng@google.com Records the result of Nearby Share starting a bandwidth upgrade via the Nearby Connections library. This metric only records the result of initiating the change not the result of fully finishing an upgrade. Also, this metric does not capture automatic bandwidth upgrades initiated internally by the Nearby Connections library. Emitted when the Nearby Connections client explicitly requests a bandwidth upgrade. crisrael@google.com nearby-share-chromeos-eng@google.com Records if the transfer medium was successfully upgraded after an explicit bandwidth upgrade request from the client. Emitted when the transfer channel is disconnected after a bandwidth upgrade request was made by the client. pushi@google.com nearby-share-chromeos-eng@google.com Records the time that it took the user to successfully complete the onboarding flow. Only emitted on successful completion of onboarding. pushi@google.com nearby-share-chromeos-eng@google.com Records how the user entered the onboarding flow. The options are from OS Settings, the tray icon and the share sheet. Emitted as soon as the user embarks on the one-time Nearby Share onboarding flow, regardless of whether or not they successfully finish. pushi@google.com nearby-share-chromeos-eng@google.com Records how users interacte with the onboarding flow. Emitted when users embark the Nearby Share onboarding flow, click buttons during the process. pushi@google.com nearby-share-chromeos-eng@google.com Records how far the user made it through the onboarding flow. The user has an option to cancel onboarding on the device name page or visibility page. Once the user confirms device visibility onboarding is complete. Emitted when the user cancels onboarding during one of the steps or on successful completion. pushi@google.com nearby-share-chromeos-eng@google.com Records the attachment types from {Variation}. Emitted after all attachment transfers conclude, successfully or not, for a given share target. crisrael@google.com nearby-share-chromeos-eng@google.com Records whether a payload transfer succeeded, failed, or was cancelled when transmitted over {UpgradedMedium}. Emitted when the payload transfer finishes, independent of whether the transfer was successful. Removed in 10/2022. Now using Nearby.Share.Payload{Operation}.Success{FilePath} to support different operation and file path types. alanding@google.com cros-sharesheet@google.com pushi@google.com nearby-share-chromeos-eng@google.com Records if a payload transfer used an upgraded bandwidth medium, and if so, which medium. Emitted when the payload transfer finishes, independent of whether the transfer was successful. crisrael@google.com nearby-share-chromeos-eng@google.com Records if a payload transfer with {ShareTargetType} used an upgraded bandwidth medium, and if so, which medium. Emitted when the payload transfer finishes if over 5MB was transferred, independent of whether the transfer was successful. pushi@google.com nearby-share-chromeos-eng@google.com Records the number of {Type} attachments intended to be sent in a Nearby Share transfer. Emitted when the transfer concludes, successfully or not. crisrael@google.com nearby-share-chromeos-eng@google.com Records the total payload size of a Nearby Share transfer {Variation}. Emitted when the transfer concludes. pushi@google.com nearby-share-chromeos-eng@google.com Records the payload transfer rate of a Nearby Share transfer {Variation}. Emitted when the transfer concludes. brandosocarras@google.com nearby-share-chromeos-eng@google.com Records the attachment types of transfers of trait {Variation} between this device and share targets with contact status {ContactStatus}. alanding@google.com cros-sharesheet@google.com nearby-share-chromeos-eng@google.com Records the success/failure of a Nearby Share file {Operation} where the file path is created within a mount point owned by file manager. Emitted when the {Operation} on file(s) from {FilePath} are completed successfully or with failure. crisrael@google.com nearby-share-chromeos-eng@google.com Records the reason Nearby Share advertising failed to start in {Mode} mode. pushi@google.com nearby-share-chromeos-eng@google.com Records the result of starting Nearby Share advertising in {Mode} mode. crisrael@google.com nearby-share-chromeos-eng@google.com Records the time from initiating a send on a share target to sending the introduction frame. This roughly measures the delay between choosing a share target to initiate a transfer and displaying the accept/reject notification on the receiving device. Emitted after the user selects a device when the introduction frame has been sent, and this is only emitted after a successful connection is established. This metric is only emitted for outgoing transfers. pushi@google.com nearby-share-chromeos-eng@google.com Records the time from accepting a share on the receiving device until the first payload byte is processed. Emitted after accepting a share when the first in progress payload transfer update is received. This metric is only emitted for incoming transfers. crisrael@google.com nearby-share-chromeos-eng@google.com Records the final status of a Nearby Share transfer {Variation}. Emitted when a transfer completes successfully, fails, or was aborted by the user, for example, by cancelling the transfer. pushi@google.com nearby-share-chromeos-eng@google.com Records the success/failure of a Nearby Share transfer. Emitted when a transfer completes successfully or definitively fails, but not for indeterminate states like cancellation. brandosocarras@google.com nearby-share-chromeos-eng@google.com Records the success/failure of a received attachment from a device, logged into the same GAIA account as the receiver, of type {ShareTargetType} while the receiver is in {DeviceState} state. Emitted when a transfer completes successfully or definitively fails, but not for indeterminate states like cancellation. crisrael@google.com nearby-share-chromeos-eng@google.com Records the success/failure of a Nearby Share {Direction} transfer with {ShareTargetType} using {ContactStatus}. Emitted when a transfer completes successfully or definitively fails, but not for indeterminate states like cancellation. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when receiver accepts the transfer to when all files are successfully transferred. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when the first bandwidth upgrade occurs to when all files are successfully transferred for {Medium}. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when the receiver decodes the incoming endpoint to when the introduction frame is received. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when a high-visibility receiver decodes an endpoint to when the first bandwidth upgrade occurs for {Medium}. In high-visibility mode, the receiver will attempt a bandwidth upgrade immediately upon decoding the endpoint. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when a non-high-visibility receiver completes the paired key handshake to when the first bandwidth upgrade occurs for {Medium}. In non-high-visibility mode, the receiver will attempt a bandwidth upgrade after a successful paired key handshake. This metric captures how long it takes to successfully complete that bandwidth upgrade. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when receiver receives the introduction frame to when all files are successfully transferred. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when the first bandwidth upgrade occurs to when all files are successfully transferred for {Medium}. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when the sender establishes a connection to when the first bandwidth upgrade occurs for {Medium}. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when a sender discovers an endpoint to when the connection was successfully established. Note: This contains user interaction so it may vary significantly. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when user selects the receiver to when all files are successfully transferred. Note: This contains user interaction so it may vary significantly. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when user selected the outgoing endpoint to when the introduction frame was sent to the receiving endpoint. jackshira@google.com dclasson@google.com nearby-share-chromeos-eng@google.com Records the time between when sender starts to transfer files to when all files are successfully transferred. pushi@google.com nearby-share-chromeos-eng@google.com Records the user's chosen degree of visibility to their contacts, selected during onboarding or updated in settings. Emitted at login for users that have Nearby Share enabled. crisrael@google.com nearby-share-chromeos-eng@google.com Records the success/failure of the Wi-Fi Network Configuration Handler. When Wi-Fi credentials are successfully received, the Configuration Handler will attempt to configure that network automatically. Emitted immediately after the transfer has completed and the Configuration Handler attempted to configure the network.