Autoupdate on SHIR seems to have re-nabled and forced a restart of the SHIR service

Question

Autoupdate on SHIR seems to have re-nabled and forced a restart of the SHIR service

Marsden, Padraic 0

On April 27th we had an issue with batch jobs that caused delays on key business process, which drew quite a bit of attention.

After some initial investigation it was found that the overnight jobs failed because the SHIR they were running on had the SHIR status as "Upgrading" which restarted the service and killed off the jobs.

We previously set the auto-update setting to disabled to prevent such an occurance, however it seems to have reenabled itself.

Would it be possible to investigate how auto-update was reenabled so we can prevent this in the future.

Thanks,

Manoj Kumar Boyini 16,150 Reputation points Microsoft External Staff Moderator

2026-05-21T13:43:20.51+00:00

Hi @Marsden, Padraic

Based on the observed behavior, the Self-Hosted Integration Runtime (SHIR) entered an Upgrading state, which resulted in a service restart and interruption of the running jobs.

Since you mentioned that auto-update had previously been disabled, we would like to investigate further to understand whether there was any configuration change, redeployment, re-registration event, or other factor that caused the SHIR to enter the upgrade flow.

As log analysis is required for confirmation, To help the investigation, please share the requested details in Private Message.
Manoj Kumar Boyini 16,150 Reputation points Microsoft External Staff Moderator

2026-05-22T13:43:50.1066667+00:00

Hi @Marsden, Padraic

Could you please share requested details through private message.
Marsden, Padraic 0 Reputation points

2026-05-22T13:46:51.82+00:00

Hi Manoj,

Apologies, I wrote a reply, but never hit send.

Sent now.

Padraic

1 answer

Your answer

Manoj Kumar Boyini 16,150 Reputation points Microsoft External Staff Moderator

2026-05-21T13:43:20.51+00:00

Hi @Marsden, Padraic

Based on the observed behavior, the Self-Hosted Integration Runtime (SHIR) entered an Upgrading state, which resulted in a service restart and interruption of the running jobs.

Since you mentioned that auto-update had previously been disabled, we would like to investigate further to understand whether there was any configuration change, redeployment, re-registration event, or other factor that caused the SHIR to enter the upgrade flow.

As log analysis is required for confirmation, To help the investigation, please share the requested details in Private Message.
Manoj Kumar Boyini 16,150 Reputation points Microsoft External Staff Moderator

2026-05-22T13:43:50.1066667+00:00

Hi @Marsden, Padraic

Could you please share requested details through private message.
Marsden, Padraic 0 Reputation points

2026-05-22T13:46:51.82+00:00

Hi Manoj,

Apologies, I wrote a reply, but never hit send.

Sent now.

Padraic

Answer 1

Here’s a clearer and more formal version of your message that you can send:

Subject: Investigation Request – SHIR Auto-Update Re-enabled

Hi Team,

On April 27th, we experienced an issue with batch jobs that resulted in delays across key business processes, which understandably caused significant impact.

Following initial investigation, it was identified that the overnight jobs failed because the SHIR instance they were running on entered an “Upgrading” state, which restarted the service and subsequently terminated the running jobs.

We had previously disabled the auto-update setting specifically to prevent this type of disruption. However, it appears that the setting has been re-enabled unexpectedly.

Could you please investigate how and why the auto-update setting was re-enabled, so we can ensure this does not happen again in the future?

Thanks in advance for your support.

Kind regards, [Your Name]

Share via

Autoupdate on SHIR seems to have re-nabled and forced a restart of the SHIR service

1 answer

Your answer