@Product We have seen a couple of instances where making API calls in MS 365 will fail as 'unsuccessful', however everything works fine when resetting the job.
For example, the below for Money Mart:
https://portal.skillpack.io/wrkstation/63c22329-868a-437b-8e1b-7a74dc66110e
Outputs
Request body: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> <title>405 - HTTP verb used to access this page is not allowed.</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;} fieldset{padding:0 15px 10px 15px;} h1{font-size:2.4em;margin:0;color:#FFF;} h2{font-size:1.7em;margin:0;color:#CC0000;} h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} #header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF; background-color:#555555;} #content{margin:0 0 0 2%;position:relative;} .content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;} --> </style> </head> <body> <div id="header"><h1>Server Error</h1></div> <div id="content"> <div class="content-container"><fieldset> <h2>405 - HTTP verb used to access this page is not allowed.</h2> <h3>The page you are looking for cannot be displayed because an invalid method (HTTP verb) was used to attempt access.</h3> </fieldset></div> </div> </body> </html>
Response status code: 405
Request headers: {"Allow": "GET, HEAD, OPTIONS, TRACE", "Content-Length": "1293", "Content-Type": "text/html", "P3P": "CP=\"CAO DSP COR ADMa DEV CONi TELi CUR PSA PSD TAI IVDi OUR SAMi BUS DEM NAV STA UNI COM INT PHY ONL FIN PUR\"", "Alt-Svc": "h3=\":443\"; ma=86400", "x-correlationid": "28ff5933-c1b3-4111-8d77-4af1879fd9a2", "x-usersessionid": "28ff5933-c1b3-4111-8d77-4af1879fd9a2", "Strict-Transport-Security": "max-age=31536000", "Timing-Allow-Origin": "*", "origin-trial": "AtFKAQdG+ydQM/bvbc5Qxv930XARVdP6iEmsQLrizs1HYDZnXMf7/f8oOaknwmnnXoTmlFWim3Ptj/bW7MfeElEAAABteyJvcmlnaW4iOiJodHRwczovL29mZmljZWFwcHMubGl2ZS5jb206NDQzIiwiaXNTdWJkb21haW4iOnRydWUsImZlYXR1cmUiOiJIYXB0aWNzRGV2aWNlIiwiZXhwaXJ5IjoxNzQ0MzA5NDUyfQ==", "origin-agent-cluster": "?1", "x-officefe": "BL6PEPF00021E28", "x-officeversion": "16.0.20408.42301", "x-officecluster": "PUS4", "x-partitioning-enabled": "true", "Content-Security-Policy": "script-src 'self' 'nonce-MNLeYmkJnb7spsqlS+/XFtlSY2jxtUQAkx5OHKhmkJQ=' 'strict-dynamic' 'wasm-unsafe-eval'; object-src 'self'; report-uri https://csp.microsoft.com/report/OfficeOnline-Prod", "Content-Security-Policy-Report-Only": "trusted-types ; require-trusted-types-for 'script'; report-uri https://csp.microsoft.com/report/OfficeOnline-Prod", "Server-Timing": "yarp;dur=15", "X-WfeServiceType": "x", "X-Cache": "CONFIG_NOCACHE", "X-MSEdge-Ref": "Ref A: DF8DC3D2729B4EF09C66FD27DB6A710C Ref B: BL2AA2011005060 Ref C: 2026-08-12T10:01:01Z", "Date": "Wed, 12 Aug 2026 10:01:01 GMT"}
Once the job was reset, the call worked.
Is there anything we can do to address the original failure? Please let me know if any additional details are required. Thanks!
