Schedule the daily recurring-payments job

Recurring payments are templates; a background job turns them into real payments on their due dates. REDA Pay ships the job but does not schedule it — an administrator does that once, in Setup. Until then every schedule your team or your customers create shows as active and never runs.

Schedule the job

1. Open Setup, type Apex Classes in the Quick Find box and click Apex Classes.
2. Click Schedule Apex at the top of the list.
3. Fill in:

1. Click Save.

The Schedule Apex page in Setup with Job Name "REDA Pay - Recurring Payments", Apex Class SchedulePayOrderJob, Frequency Weekly with all seven days ticked, start and end dates and a preferred start time

One job, every day. The time you choose is when the day's recurring payments are taken.

What the job does each day

1. Finds every Pay Order of type Schedule whose Schedule Active is on and whose Schedule Next Run Date is today.
2. Clones each into a new Immediate Pay Order linked back by Parent Pay Order, then processes those orders one at a time — registering nothing new, because the customer and method were registered when the schedule was created.
3. Sets each schedule's Schedule Last Run Date, which moves Schedule Next Run Date forward and adds one to System Run Instances.
4. Writes a REDA Pay Log if anything failed, and the order owner gets "Scheduled Payment [P-000000] failed." for each failed run.

A run that fails is not retried; the schedule simply continues on its next date. See Set up a recurring payment.

Check it is running

Worked example: one morning's run

Three schedules are due on 1 November: two residents' rent by bank account and one owner-services fee by card.

A REDA Pay Log for the run records two failures with the two orders and their errors in the attached file, and the administrators receive the "ATTENTION NEEDED" email. Collections follows up the two failed runs; the schedules themselves need no change unless the card is replaced.

Choosing the hour

The time you pick is in the time zone of the user who schedules the job. An early hour before the business day means failures are waiting in the Attention Needed view when staff arrive, and payers see a consistent charge time. Avoid the top of the hour your other heavy jobs run; the REDA Pay job calls Payload once per schedule and is quick, but it competes for the same batch slots.

Running it more than once a day, or for a past date

The job runs once per day by design: schedules are keyed on dates, and a second run on the same day finds nothing new to do. If the job was missed on a day — for example it was not yet scheduled, or the org was unavailable — an administrator can run it for that date from the Developer Console (Debug → Open Execute Anonymous Window):

rpay.SchedulePayOrderJob job = new rpay.SchedulePayOrderJob();
job.processDate = Date.newInstance(2026, 11, 1);   // the missed date
System.schedule('REDA Pay - catch-up ' + String.valueOf(DateTime.now().getTime()), '0 0 * * * ?', job);

This schedules a one-off run at the next hour for the given date; schedules due on that date and not yet run are processed. The job also accepts batchSize (default 50) for the number of schedules handled per batch.

Mistakes to avoid

FAQ

Where to go next

• Turn on failed-payment recovery
• Set up a recurring payment