Job results are not available when executing custom scripts via the runscript command #14549
Labels
severity: medium
Results in substantial degraded or broken functionality for specfic workflows
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Deployment Type
Self-hosted
NetBox Version
v3.6.6
Python Version
3.11
Steps to Reproduce
runscript
commandExpected Behavior
Script is completed and job results are available
Observed Behavior
Script gets completed, but a KeyError exception gets raised when trying to access the job results
It seems that an incorrect name tries to get accessed when the script is ran through the
runscript
command, as compared to running the script via the GUIThe text was updated successfully, but these errors were encountered: