Technical Tip: Error of 'Input value is invalid - Invalid unsigned integer value' when editing route-map in FortiGate GUI

[tino_p]

Description	This article describes the error of 'Input value is invalid - Invalid unsigned integer value' when editing route-map in the FortiGate GUI. However, editing the route-map in FortiGate CLI still works normally.
Scope	FortiGate GUI of v7.4.4, BGP.
Solution	When running the httpsd debug: diagnose debug console timestamp enable diagnose debug app httpsd -1 diagnose debug cli 8 diagnose debug cmdb-trace 1 diagnose debug enable It showed the following error: "... 2025-07-02 10:33:17 [httpsd 31683 - 1751427197 info] fweb_debug_final[355] -- Completed PUT request for "/api/v2/cmdb/router/route-map/CHANGE_NEXTHOP" (HTTP 500) 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 info] fweb_debug_init[513] -- New POST request for "/api/v2/monitor/system/debug" from "10.61.124.165:63342" 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 info] fweb_debug_init[515] -- User-Agent: "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0" 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 info] fweb_debug_init[517] -- Handler "api_monitor_v2-handler" assigned to request 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 info] api_store_parameter[327] -- add API parameter 'messages' (type=array) 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 info] endpoint_process_req_vdom[1076] -- new API request (action='select',path='system',name='debug',vdom='root',user='admin') 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 warning] JavaScript -- FOSError: -651: Input value is invalid. 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 warning] JavaScript -- Possibly unhandled rejection: {"user_notified":"error","http_method":"PUT","revision":"eaafb81e3e5b7fcb395312ac4b243635", "revision_changed":false,"cli_error":"<strong>Input value is invalid.</strong><br><ul class=\"error-msg-list\"><li>Invalid unsigned integer value:.</li></ul>","error":-651,"status":"error","http_status":500,"vdom":"root","path":"router","name":"route-map","mkey":"CHANGE_NEXTHOP","serial":"FG2K2ET921900324","version":"v7.4.4","build":2662} processChecks@https://10.80.16.153/static/ng/app.js:2:2167978 $digest@https://10.80.16.153/static/ng/app.js:2:2178940 26090/bootstrap/</</Xi<@https://10.80.16.153/static/main.js:1:2848731 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 warning] JavaScript -- Possibly unhandled rejection: undefined processChecks@https://10.80.16.153/static/ng/app.js:2:2167978 $digest@https://10.80.16.153/static/ng/app.js:2:2178940 26090/bootstrap/</</Xi<@https://10.80.16.153/static/main.js:1:2848731 2025-07-02 10:33:18 [httpsd 31673 - 1751427198 warning] JavaScript -- Possibly unhandled rejection: undefined processChecks@https://10.80.16.153/static/ng/app.js:2:2167978 $digest@https://10.80.16.153/static/ng/app.js:2:2178940 26090/bootstrap/</</Xi<@https://10.80.16.153/static/main.js:1:2848731 ..." The workaround is to use FortiGate CLI to edit the route-map. The solution is to upgrade the Firewall firmware to v7.4.8 or v7.6.0.