/v4.0/words/convert intermittently fails with timeout errors

Aspose.Words Cloud Product Family
21

@diZane22
I checked the logs and this is what I found
this is a request body you sent when the response is 200 and valid

"{\"FileName\":\"relatorio_Viveiros Europlantas Lda.pdf\",\"SaveFormat\":\"pdf\"}"

and this is when you get an error, well at least in the requests that are successfully pass to our service

"\"\\\"SaveFormat\\\": \\\"pdf\\\", \\\"FileName\\\": \\\"teste999.pdf\\\" }\""

request body is not a valid json object

22

Hi @yaroslaw.ekimov,

Thanks for digging into this — that confirms something, but I think it’s a separate issue from the one currently blocking me.

That malformed body (teste999.pdf) is from an earlier troubleshooting attempt, when I was testing Make.com’s native “Make an API Call” action for the Aspose connector. I’d noticed independently that this specific action seems to wrap the entire request body in an extra layer of JSON string escaping before sending it — so {"SaveFormat": "pdf", ...} arrives as a JSON-encoded string rather than a JSON object. Your log confirms that’s exactly what happened. Good to have it confirmed server-side, but I’ve since stopped using that action because of this.

The issue currently blocking me is different and separate: it’s the native “Save a File as” action (and also “Convert a File”), which doesn’t involve any hand-typed JSON — it uses Make’s own structured fields (Name, Format, FileName). That one doesn’t return any JSON parsing error at all — it just times out after ~40s with no response whatsoever (ModuleTimeoutError, no requestId, nothing in your logs to match against, since no response ever came back).

So to be clear, there seem to be two distinct problems:

  1. “Make an API Call” — sends a malformed (double-escaped) JSON body → now confirmed, I’ve stopped using it.
  2. “Save a File as” / “Convert a File” — the actual blocker — times out with zero response, even with correctly-formed requests (confirmed this also happens with a plain HTTP call outside your connector, and with reqbin.com, using a fresh valid token each time).

Could you check the logs specifically for requests to relatorio_ViveirosEuroplantasLda.docx/saveAs (or /convert) around 2026-08-24 10:37 UTC — those are the ones that never got a response at all, which is the one I actually need resolved?

Thanks again for looking into this.

23

@diZane22
Thanks for clarifying, I looked more precisely at the requests, and what I found is the duration of conversion sometimes around 42-43 seconds at our end, so that’s why you got timeouts after 40 sec, it seems that you need to increase timeouts for that document.
Please share that document for analysis, you can send it via private message.