ConnectionError [504] - Error Code: 504 with Anthropic Claude Module

Emir_Corovic · August 29, 2025, 12:24am

What are you trying to achieve?

I am trying to use the Anthropic Claude module in my workflow to process various requests and generate responses. However, I am suddenly encountering a persistent ConnectionError [504] regardless of the input content or prompt provided.

Steps taken so far

I have been using the Anthropic Claude module successfully without issues until very recently.
No configuration changes have been made on my end, such as API keys, model selections, or environment settings.
I attempted to run multiple operations with different inputs (e.g., simple prompts, complex queries), but the error persists in every case.
I checked my internet connection and local setup, which appear stable and unchanged.
I implemented error handlers that retry the operation up to 3 times, with a 30-minute interval between each attempt, but the same error occurs every time.
The error occurs immediately during the initialization or operation phase, as shown in the attached screenshots.

Screenshots: scenario setup, module configuration, errors

samliew · August 29, 2025, 1:52am

Welcome to the Make community!

Have you tried reconnecting the connection in the Connections page?
Have you tried setting up a new connection?

Hope this helps! Let me know if there are any further questions or issues.

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

Emir_Corovic · August 29, 2025, 2:51am

Hello @samliew ,

Claude don’t need any reconnection but i checked connections tab and there is everything okay.

Thank you for trying to help me.

Emir_Corovic · August 29, 2025, 3:03am

Waow after 9 retries in 3 Hours timeframe it succeded for some reason.

Thats kinda really strange, if i run a SaaS and many clients got problem cuz of that, thats not so cool.

samliew · August 29, 2025, 3:12am

This had better be reported to Make support, as it is likely to do with server-to-server communication issues.

Contact Make Support

For technical issues or bugs like this, contacting Make support by creating a ticket is the official option available to paid Make customers. If you are a free customer, I recommend that you get a free Pro plan to get quicker support via the ticketing system.

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 also be able to reach out to the custom app developer. 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.

How to Create a Support Ticket

If you are logged-in, you can head to the new ticket page to submit a ticket. (If you are unable to login to your main account, it is advised to create a free Pro account to access this 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 daily, therefore they have to prioritise tickets based on the organisation’s subscription plan. For more information about the different levels of customer support, refer to the “Support” section on the Pricing page, or on your organisation’s Subscription tab. If you are a free customer, I recommend that you get a free Pro plan to get quicker support via the ticketing system.

Resolution

When your issue is resolved one way or another, we’d love to hear more details about the cause, and how you managed to solve it (including use of workarounds). By sharing your findings and solutions, we are contributing to this knowledgebase to enable others to search for answers to similar problems.