Send Files to One Device on a Recurring Schedule With Follow-Up Actions

Automate recurring file delivery to one destination device and configure follow-up actions after each completed transfer.

  • Send files
  • One device
  • On a recurring schedule
  • Follow-up actions

Start conditions

When should it start?

File options

After transfer

You can add more than one action.

What should happen after the transfer?

Your example is ready.

Download the generated example

Download a runnable example for the transfer you configured.

Choose a language

Transfer Example, JavaSource code, run configuration, README (a complete project generated for your configuration)ZIP

or Download from Git

No sign-up needed to download.

Run the example

Set it up in QuickConnect the devices and download the .env file
Run the example locallyApply the .env file, then follow the README

Running a real transfer needs an INNORIX Platform account.

Frequently asked questions

Find answers to the most common questions about this configuration.

  • Can recurring transfers run follow-up actions?

    Use this configuration when recurring transfer and follow-up actions are supported together.

  • Do follow-up actions run after every scheduled transfer?

    Confirm the trigger and completion rules for each execution in the product documentation.

  • How can I troubleshoot repeated transfer failures?

    Review the recurrence settings, destination availability, execution history, and error logs.