The scheduled job instance is skipped . Oracle Analytics Publisher defines a Schedule Trigger as a SQL query that is executed when the scheduled report job is triggered, before the report itself runs. The returned result determines whether the execution condition has been satisfied.

Oracle states explicitly that if the trigger SQL returns data , the associated report job executes. If the SQL query returns no data , the job instance is skipped. This mechanism allows report execution to depend on a business or technical condition. For example, a report could execute only after an ETL process has completed, only when transactions exceed a specified amount, or only when new records have appeared.

The trigger doesn't convert the job into a bursting job, nor does Publisher execute an empty report merely with a warning. The scheduled job definition also isn't deleted; only that execution instance is skipped. For recurring schedules, subsequent trigger evaluations can still occur according to the configured recurrence and retry behavior.

Therefore, a no-row result from the Schedule Trigger means its condition evaluated as not satisfied and the current job instance is skipped .

Reference Topic: Managing Report Scheduling, Data Sources, Administration, and Translations — Schedule Triggers

===============