Select to view content in your preferred language

Scheduled notebooks failing

355
6
2 weeks ago
tssau
by
Emerging Contributor

All scheduled daily notebooks on AGOL have been failing since 10/29/2025. Even with a newly created notebook that only does print('test').

 

Here is the result of the task:

{
  "error": {
    "code": 90031,
    "message": "Invalid value for executionTimeoutInMinutes for notebook job run.",
    "messageCode": "NBO_90031",
    "details": []
  }
}

 AGOL bug?

Tags (2)
6 Replies
OllyD
by
Occasional Contributor

We've been having the same issue, this also started happening the 10th of October. 

Every time there's an AGOL update something seems to unexpectedly break.....

0 Kudos
LWWCGIS
Occasional Contributor

Same issue for us. Oct, 29 is when ours started failing too. AGOL updates these days now feel like 1 step forward and 2 steps back.

0 Kudos
WildfireFL
New Contributor

I am also having the same problem. Interestingly, one of our notebook tasks is still running successfully. The other notebooks that are failing as tasks are able to run manually.

Paco_VanSistine
Emerging Contributor

Agreed.  same timeframe for our sudden "executionTimeoutInMinutes" Errors.   but as mentioned,  the Notebook scripts run manually without Error.

0 Kudos
LWWCGIS
Occasional Contributor

I updated a notebook runtime to standard 12 yesterday, reactivated it, and it actually ran on its own this morning.

RaviNarayanan
Esri Contributor

Hello All, 

Thank you for this posting. A recent change to enforce the maximum execution timeout for scheduled task led to this error. Any tasks that have a maximum execution timeout set to a value greater than 1425 minutes failed with that error. A fix has been posted so those tasks should no longer fail. When you create any  tasks new tasks please ensure that default timeout value is set to 1425 minutes or less. We will be adjusting the UI to ensure the default timeout value is 1425 or less in a future update.

Thank you.