REST Countries API module slow response causes scenarios to error

Hi is anyone else finding recent problems with the REST Countries API module?

I have been using this in a few scenarios for years without issues, but recently for the last week, my scenarios have been erroring as they are getting stuck on this module.

They do eventually go through when starting via a webhook, but it usually takes about 4 error runs before it works.

Has anyone else experienced this?

A workaround could be to use the ‘HTTP - Make a request’ module instead, but I have a very large number of modules that refer to REST Countries, so this would be a huge amount of updates, so I’m hoping it will resolve.

I thought this was a module but can’t find who the developers are to contact about this.

I’d be interested to hear anyone else who has had this and ideally any solutions / signs of hope!
Screenshot 2024-05-29 at 11.51.37

Welcome to the Make community!

This could be intermittent server issues on the external service.

Handle errors so scenarios don’t stop.

You might want to add some error handling to your modules to handle exceptions, so the failing module(s) can automatically be retried or ignored. By handling any errors by adding a “Error handler” to the module, the scenario won’t throw an error and get turned off.

Error directives can only be added to an error handler route.

1. Right click and select “Add error handler”


2. Error handlers will appear

For more information on error handling, see:

samliewrequest private consultation

Join the unofficial Make Discord server to chat with other makers!


Thanks so much for the idea @samliew

I have used a few error handlers, not extensively, so this didn’t occur to me. I like the way I then wouldn’t need to update all my following modules.

I suppose I’d have to go without the info I’m getting from this module in the cases that this module errors, but overall in terms of trade-offs, this may be better than the whole scenario stopping.

Thank you very much for the great practical idea.


Adding a break error handler will solve your problem. It will retry if there is some issue in the module.

@VinayakUpadhyay thank you for the specifics which helped me read up on this. I will test adding a Break error handler, and it looks like automatic resolution of errors would probably be the best option to try.

I will leave this thread open as I’d like to report back, which may help others too.

Hi @Sarah_D did you found any solution for this issue, I am also facing same issue for REST Countries API slow response/no response.

Welcome to the Make community!

For technical issues like this, directly contacting support can often lead to a faster resolution. They have access to server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

Join the Make Fans Discord server to chat with other makers!


Hi @Madhur_Patil not yet, I am hoping it will get resolved by the authors of REST Countries.

Make Support suggested an HTTP request to REST Countries could help, but this also timed out.

In the meantime, I have had to make a duplicate backup scenario without this module, as it was stopping mine running.


@VinayakUpadhyay thank you again, I did try the Break error handler, but I think the issue with the REST Countries module is still also preventing even the error handler working for now.

@Sarah_D do you know any info about authors? so we can reach out to them

@Madhur_Patil have a look/ post here. This is what I found by googling. Currently my requests timeout or i get super slow response times (#230) · Issues · restcountries / restcountries · GitLab

You should really contact support first, because they can perform an emergency update while contacting the app developer officially.

samliewrequest private consultation

Join the unofficial Make Discord server to chat with us!

1 Like

Thanks @Sarah_D , its working now I guess

This is interesting. Support told me to contact the app developer myself, but would be useful if they could do as you suggest here.

Solution here for anyone following

  • wait for it to resolve
  • use Break error handler if the delay isn’t too long (as it was here)
  • contact app developer/ ask Support to do so

In this case, the app developer resolved the issue in a couple of weeks.


Hey there @Sarah_D :wave:

Just wanted to jump in and thank you for your regular updates about this issue.

We appreciate that you kept us in the loop. :pray:

1 Like