Oauth2 credential not being requested after expiration using HTTP v4 and Microsoft Graph and an app registration

:bullseye: What is your goal?

Figure out how to get HTTP v4 oauth2 to send a new token request with each request.

:thinking: What is the problem & what have you tried?

I’ve made a scenario that access the MS Graph and pulls data. Is configured using HTTP v4 and oauth2 credential store. This has been working fine, until my token expires. Once that is done I get a “this token is expired” instead of make just hitting the end point for a new token.

If I go to the “connections” tab and hit requthorize, it works fine again for an hour, until it expires once more.

I’m not sure what I’m doing wrong here, since I’m using an app registration client/secret instead of delegated access I shouldn’t need offline_access or refresh tokens, as that is for delegated access only. Docs state best practice is to always ask for a new token on run but the module doesn’t seem to be doing that?

Any guidance on how to address this?

:clipboard: Error messages or input/output bundles

Error
Unauthorized

  • {“error”:{“code”:“InvalidAuthenticationToken”,“message”:“Lifetime validation failed, the token is expired.”,“innerError”:{“date”:“2026-01-12T23:22:26”,“request-id”:“*****************”,“client-request-id”:“****************************”}}}

Welcome to the Make community!

I’m not exactly sure if this is a bug, but you might be able to use the Make API to reverify the connection, which may fetch a new token.

Endpoint: Connections | Make API | Make Developer Hub

If you need further assistance, please provide additional details on how you’ve set up the connection, including providing screenshots.

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 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 advisable to create an account to access this page.)

Screenshot of the Contact Support page
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 daily, 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 issue is resolved one way or another, we’d love to hear details about the root cause, and how support and you worked to solve it (including use of any workarounds). By sharing your findings and solutions, 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!