I've been working on my first Azure Runbook, which I developed in Python. Here's the sequence of events:
1. I built and successfully tested the script in VS Code on my machine.
2. I added all the necessary Python modules to the Azure Runtime Environment (Python 3.10) that I'm using.
3. I tested it from the Azure Portal's test pane and it worked well.
4. I triggered it using a webhook around 1 PM, but accidentally stopped it while checking the job's details after it had been running for about 21 minutes.
5. Now, all subsequent executions of this job have failed after roughly 3 minutes without clear error details. I attached a snapshot of the Exception panel showing just the script's log output.
Can anyone help me figure out what might be going wrong? *Edit: I'm using a Visual Studio Enterprise subscription.*
3 Answers
It looks like the error sourced from your exception message is what’s causing the runbook to fail. The fact that you stopped the runbook doesn’t seem to be related to the issue at all.
In my experience, when I run the job from the test pane it processes all 1500 files without issue. But during the failed jobs, it only manages between 500 and 600 files each time, which seems variable. This might indicate a timeout issue or some sort of threshold being reached. I’m planning to add logging to check the exact timing of the executions to see if this correlates with the 3-minute failure.
You might want to start adding logging to your code to see where the runbook is getting stuck. It could provide insight into what's going wrong.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically