Integration with Klaviyo "Sorry, something went wrong. Please try again later." issue

[IvanCyber]

@magento this is my issue:

Preconditions (*)

Magento ver. 2.4.2

Steps to reproduce (*)

1. I Login in Magento2 with admin credentials.
2. In Magento2 administration, Stores -> Configuration -> Klaviyo is properly set, and I see the Klaviyo lists there in the dropdown list.
3. When I go to Magento administration, System -> Integrations and click "Add new integration",

• I set name, my e-mail,
• I set Callback url: https://www.klaviyo.com/integration-oauth-one/magento-two/auth/confirm?c=XXXXXXX
• I set Identity link URL: https://www.klaviyo.com/integration-oauth-one/magento-two/auth/handle
• I set my Magento2 admin pass
• Go to API tab and in Resource Access dropdown list I set "All", and
• Click "Save", it is being saved, with note that the data are saved, but the new user is not created, because the old one is overwritten and updated.

Expected result (*)

1. When I go to System -> Integrations and click on "Activate", I expect activated integration, so that I can finish integration in Klaviyo.

Actual result (*)

1. When I go to System -> Integrations and click on "Activate", I get the window with note "The integration you selected asks you to approve access to the following:" and all the selected resources are listed. I click on "Allow" window and I get "Sorry, something went wrong. Please try again later.".
2. When I go to see the integration, what I see is that "Consumer Key" and "Consumer Secret" fields are filled, but "Access Token" and "Access Token Secret" are empty.

What am I doing wrong?

[m2-assistant]

Hi @IvanCyber. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[IvanCyber]

@magento I am working on this

[m2-assistant]

Hi @IvanCyber! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[m2-assistant]

Hi @engcom-Golf. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[jorgb90]

Hi @IvanCyber ,

This wil fix your issue; 68d2023

[magento-engcom-team]

@engcom-Golf Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!