Skip to content

Compliance control fails with "External joint torque exceeds threshold" after firmware update #222

Compliance control fails with "External joint torque exceeds threshold" after firmware update

Compliance control fails with "External joint torque exceeds threshold" after firmware update #222

Triggered via issue March 23, 2026 02:24
Status Failure
Total duration 9s
Artifacts

issue_bot.yml

on: issue_comment
add-question-label
add-question-label
mark-answered-by-org-members
5s
mark-answered-by-org-members
close-answered-after-week
close-answered-after-week
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
mark-answered-by-org-members
Resource not accessible by integration
mark-answered-by-org-members
HttpError: Resource not accessible by integration
mark-answered-by-org-members
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-ecosystem/action-add-labels@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/