Hi Tim,

Maybe the adaptation for OutSystems don't use all codes from the original Library.

Is possible that the way it was implemented in OutSystems use some custom validations, since it was not a requisite back there to the developer to use all codes.

Looking for the post you linked from github, seems like this table of codes is not an original documentation, it is just a sample that some user provided, it may even exist more errors and scenarios than the ones listed, if I understand correctly.

Any way, maybe the reason the code 1 is not considered in the component as a valid return is that some part of the file could be missing due the failed requests.

You can always customize it for your needs if you want to add code 1 as a valid return.

But is also cool to wait for the feedback of the component's developer.

Cheers and Regards,

RR :)

Raphael, thank you for your input.

I did check the .net code, which directly calls the wkhtmltopdf.exe and the lines of code capture the return code of that exe process, so there is no OutSystems interpretation or validation.

I know there is no official documentation on github stating the return codes (which is why I put it between ") but this is as close as I can get. I audited the whole .net code in an effort to find the true exception, because the component does a great job at hiding it. I noticed getting 1, which the code interprets as error. In dev it works with exactly the same code, so it must be returning 0 or 2 there.