We have webjobs that exports our registrations to a blob container:

var exportJob = await client.SubmitNotificationHubJobAsync(new NotificationHubJob
{
    JobType = NotificationHubJobType.ExportRegistrations,
    OutputContainerUri = exportBlobContainerSasUri
});

This creates an Output.txt and also apparently a empty test.json file. When enabling blob container logging we can see that the job tries to delete this test.json file directly after creating it but since we gave the job a SAS url without delete permissions it fails to delete this file.

Not a big deal but now we have a situation where two export job instances seem to have stuck in an endless loop of creating and trying to delete this test.json.

Looking at the logs we can see that two job instances every fifth minute does a PubBlob and then a DeleteBlob operation for test.json. It’s unclear how log this has ben going on, at least for a couple of weeks, maybe even for two months.

When we delete the test.json manually they get recreated within the five minute window. We did not use a SAP for the SAS so we can not easily disable the jobs ability to write to the blob container.

How do we kill these two zombie exports job?