When I receive a pdf report via IFS Cloud (23R1), exceed. The result is returned as on the screen and the output preview does not work. I will clear the print_job_tab table, but I'm not sure it will be a good solution. Has anyone encountered this problem? Thanks..
Page 1 / 1
Hi @asahin, Could you check if there are any jobs that are printing? This can cause this notification to pop up.
I remember I had an issue where reports would keep jumping between waiting and executing causing to completely occupy the print job queue.
Yes that's true. As a result we cannot print pdf reports
Could you check if you can see a job that keeps jumping back and forth between status?
how you can check,
open print manager
filter on status waiting & working
Press refresh at the top here or “apply”
If one print job keeps jumping between statusses, please contact support or your dba (in case it's hosted by your company). A specific trigger on that table should be disabled and enabled.
It's a trigger that sets waiting to working, but because of an error in the document it keeps generating.
You can ask IFS support to check ticket CS0226945 and if it's a similar problem.
We got a fix in a service update for this.
Hope it helps!
Hi @asahin,
The error message below is not, in fact, an error message.!
English error message: Report **${ReportTitle}** is taking more time than expected and currently executing in the background. Once completed, a notification will be posted. The report will be available in the Report Archive Documents with the Result Key/Print Job ID **${ResultKey}/${PreviewResult.PrintJobId}**.
This is an INFO message, generated by the Reporting Framework, indicates that the report is currently being processed in the background. Upon completion of the report generation, you may access the finished report via the 'Report Archive' window using the Result Key/Print Job ID. According to the application design, this is the expected behavior for reports which takes some time to process.
Additionally, it will be required to check ifsapp-reporting pod logs if this happens frequently.
First of all, thank you very much for your valuable feedback. Interestingly, I solved the problem by restarting IFS.