Skip to main content
Question

Shopware 6 Integration: Scheduled_Tasks stuck | data not synced from and to Klaviyo


Forum|alt.badge.img+1

Hi,

 

since upgrading our Shopware store to 6.6.x and the Klaviyo Plugin from Overdose Digital to version 3.3.x (recommended for SW6.6), we’re facing issues.

I opened up a ticket via the Google Forms link provided on the Shopware Integration docs here: https://help.klaviyo.com/hc/en-us/articles/13001662470939#h_01HBC3PT82ESVQCM2KR7GGVC80.

 

That was about a week ago. I haven’t heard anything since - not even a confirmation for posting my request. It is a bit of an odd support experience so far, with the forms and all.

Now I’m wondering if this is still the correct way to request support on the plugin as I’m kind of in the dark on if anything is happening or not.

 

The issue:

All the scheduled_tasks related to Klaviyo get stuck in status queued. We’re using a systemd-service to trigger the scheduled_tasks as well as multiple instances of the messenger-consumers. This works for all other plugins and shop-processes so far.
Scheduling the Klaviyo jobs manually it works once. Then they get stuck again for the next automated run. Sometimes the manually started jobs run for hours even though they should be running every few minutes and finish before the next run.
This produces the error “od_klaviyo.ERROR: Job is already running” when manually triggering the scheduled tasks e.g. 2 hours after the last.

 

As these tasks are not running, profiles aren’t synced between Shopware and Klaviyo. Double Opt-In consents are not synced back to Shopware. Tracking information is not synced to Klaviyo.
Unless starting it manually of course. Causing customers to e.g. sign up to a newsletter with a Shopware form (some are Klaviyo forms, some Shopware) and receiving any related mails such as the double opt-in hours after signing up.

 

Logs are set to debug and do not show any other errors outside of the above mentioned.

 

Any help or hints are appreciated. Even just knowing someone is taking care of my Google Forms request would be helpful.

Thanks!

Nico

Did this topic or the replies in the thread help you find an answer to your question?

5 replies

Byrne C
Community Manager
Forum|alt.badge.img+17
  • Community Manager
  • 140 replies
  • March 21, 2025

Hey ​@CP-Nico,

Sorry you haven’t received a response yet. I reached out to our team to check on the status of your request. Which email address and company did you use to fill out the form, if you don’t mind sharing? You can always DM me this info if you’d rather not share publicly.

While I don’t have an answer to your question at the moment, I’m going to work to make sure it gets answered. I’ll keep you in the loop.

-Byrne.


Forum|alt.badge.img+1
  • Author
  • Contributor IV
  • 8 replies
  • March 22, 2025

Hey ​@Byrne C,

thanks! I did receive an email shortly before your reply.

I’ll keep this thread open for now in case somebody from the community is able to help as well and will post our solution (if we find it) here as well.

 

Cheers,

Nico


Forum|alt.badge.img+4
  • Problem Solver III
  • 22 replies
  • March 23, 2025

It sounds like the issue likely happened because the system was mistakenly recognizing customers as renewed too early. This could happen due to:

 

1. Conditional Split Settings: The conditions used to check if a renewal has occurred might not have been specific enough. For example, it could have been looking at general order data instead of checking for a new renewal or specific order status.

 

2. Data Syncing Issues: If the order data wasn't synced or updated correctly in Klaviyo, the system might have incorrectly flagged a customer as having renewed when they hadn't.

 

3. Timing of the Flow: If the wait times between the reminder emails were too short, it could have caused the system to trigger the "thank you" email before the actual renewal took place.

 

By making sure the conditional split and order data sync are both correctly set up, you'll avoid the premature "thank you" emails.

Let me know if you need further help.


Forum|alt.badge.img+1
  • Author
  • Contributor IV
  • 8 replies
  • March 24, 2025

Hey ​@Ojuade Peace,

I believe you replied to the wrong thread there. :)

 


emma.owens
Community Manager
Forum|alt.badge.img+13
  • Community Manager
  • 119 replies
  • March 25, 2025

Hi ​@CP-Nico ! 

Checking in to see if you ever found a solution for this! 


Reply