To clarify, we have scheduled Outputs that are working, to the same database but different tables.
We have a problem one, however. You can run the search manually, verify that it works. You can then pipe it to the dbxoutput command, specifying the name of the output, and that works fine.
As soon as you go into the Output and put a cron schedule in there, it fails. The only entry in the logs is "org.easybatch.core.job.BatchJob - Job 'xxx' finished with status: FAILED ". It fails immediately, with that error message occuring in .3 seconds.
Anyone seen this?
... View more