Skip Navigation

Search

Job Scheduler – Why is my Job Execution Log truncated?
Answer ID 13149   |   Last Review Date 06/17/2026

Why is the Log Column truncated in the Job Execution Details report?

Environment:

Oracle B2C Service, All versions including Browser User Interface (BUI)

Issue:

The Job Execution Details tab in Job Scheduler may not load when the job execution log contains a very large output.

Resolution:

To help prevent this issue, the job execution log will be automatically truncated after 50,000 bytes. When truncation occurs, three dots (...) are appended to indicate that the log output was shortened.

Custom job scripts must keep their output within this limit. If a script generates a large report or verbose output, it should print only a concise summary or essential details to the script output and store the complete output separately.

 

 

Notify Me
The page will refresh upon submission. Any pending input will be lost.