Scheduling error: Invalid time format in restrict[0].time[1] despite correct input

[Mohamed_Abdallah]

What is your goal?

I want to schedule my Make.com scenario to run daily at two specific times (15:00 and 21:00).

What is the problem?

I am trying to set a daily schedule with two times: 15:00 and 21:00.

Both times are in the correct H:mm format and the timezone is Africa/Cairo.

However, I keep getting a validation error related to scheduling.

I have already tried:

• Deleting and re-adding the times manually
• Making sure there are no spaces or formatting issues
• Turning scheduling OFF and ON again
• Saving and reopening the scenario
• Reordering the times

The issue still persists, even though the inputs look correct in the UI.

It seems like there might be a hidden or cached invalid value in the scheduling configuration.

Screenshots: scenario setup, module configuration, errors

[mszymkowiak]

Hello,

Please try setting the scheduling to On demand, save the scenario, refresh the page, and run it again.

If the error persists, contact Make.com support directly.

Have a nice day,
Michal

[samliew]

Welcome to the Make community!

This appears to be a bug related to this new feature: 🔥 Feature Spotlight: More control in automation scheduling

Therefore, if you are still experiencing issues, please try contacting support directly.

Contact Make Support

As this is a community (peer-led) forum, we can only help with using the Make platform as intended (scenario building, troubleshooting scenario/module error messages, etc.). We cannot assist with account, billing, platform availability, technical issues, or bugs with the underlying software.

Make support has access to your specific account details, scenario, execution history, server-side logs, and has internal tools to investigate the issue further. If the issue is with a custom app, Make support will be able to reach out to the external team responsible for maintaining it. Also, you might need to share potentially sensitive information about your account, organisation, scenario, and execution history logs, which is not advisable here on this public forum.

Search for Updates First

Before creating a support ticket, do try to look around if others are facing the same problem, and if there are further steps you can take. Here are some things you can do —

1. Check the Make Status page to see if it is an ongoing network-wide issue/outage and view any updates (example).

2. Search this Make forum to see if there are any discussions, updates, and workarounds. Here are some possible search terms you can use:
   tags:error  bug  "not working"

How to Create a Support Ticket

• If you are unable to log-in, you should use this form to report and resolve your account’s login issue first.

• When you are logged in to your account, head to the new ticket page to submit a ticket.
  
  ^{Above: Screenshot of the Contact Support page}

After submitting your support ticket, you should receive a confirmation email with the subject “Ticket Created” together with a summary of what you submitted. If you do not receive this automated reply within minutes, try creating a ticket again. Example of email subject: [#1234567] Ticket created | Technical challenge

Priority of Tickets

If you do not receive a response from Make support, simply be patient. Make support receives thousands of tickets, hence tickets have to be prioritised based on the severity of the incidents and organisation’s plan. For more information about the different levels of customer support for each plan, refer to the “Support” section on the Pricing page, or on your organisation’s Subscription page. If you are a free customer, you can create a temporary free Pro account to get quicker support via the ticketing system.

Resolution

When your ticket has an update and/or issue is resolved, we’d love to hear details about it, and how support and you worked to resolve it (including use of any workarounds). By posting your findings and solutions in this thread, we are contributing to this knowledgebase to enable others with similar problems to search for answers.

— @samliew
_{P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!}

[Lukas_Novotny]

This scheduling validation error is a bit of a gotcha in Make. The restrict time fields in scheduling settings expect the time in a specific format, and even if the value looks correct visually, a subtle mismatch - like a missing leading zero, a timezone offset issue, or a 12h vs 24h format conflict - will trigger that error.

The restrict[0].time[1] reference points to the end time of the first time restriction block. The format Make expects is HH:MM in 24-hour notation, so 09:00 rather than 9:00, and 13:30 rather than 1:30 PM.

If you are setting this through the UI and still seeing the error, try removing the restriction entirely, saving, then re-adding it. There is a known edge case where the time picker can submit a malformed value if the field is edited rather than set fresh.

If you are setting the schedule via API or blueprint import, double-check the raw value in the exported blueprint JSON - it should be a string like 09:00, not a number or a datetime. Once I corrected the format on a scenario I was working on, the error disappeared immediately. What does your current restriction look like - is it set through the UI or imported?