A Custom Event that triggers a Deferred_Call to create a new print job (backed by a Report Rule that prints it) works correctly overall, but the background job log repeatedly shows 'Unable to register new print job... same report already being processed' — even after moving the deferred call to different batch queues. What's the actual root cause and fix?

All FAQ questions / Platform, Aurena, and customization

Answer

This is usually caused by the Custom Event itself firing more times than intended for what should be a single logical occurrence, rather than anything wrong with the print-job/batch-queue mechanism itself. Scope the event's trigger condition specifically to the exact field transition that represents the real one-time occurrence you care about — for example, firing only when a specific 'arrival' flag changes from OLD:false to NEW:true, rather than a broader condition that can incidentally match multiple times for related updates to the same record. Narrowing the trigger condition this way stops the event from re-firing redundantly, which eliminates the duplicate print-job-registration attempts and the resulting error entirely.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions