A custom Currency Rate Update workflow runs correctly when triggered manually (button click / Start Now) but never actually creates currency rates when triggered by its scheduled Database Task, even though the background job itself reports as triggered successfully.

All FAQ questions / Workflows and automation

Answer

Check whether the workflow uses the exact standard naming convention expected for the currency-rate-update integration — the scheduled task path for currency updates expects to find and invoke a specifically-named standard workflow, so a custom workflow built from scratch with a non-standard name can work fine when invoked directly (by button/projection action) but silently fail to be picked up by the scheduled mechanism, which is looking for that specific expected workflow rather than just any workflow wired to the same projection actions.

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

← Browse Workflows and automation questions