SiteContext lost in marketing automation after a wait action

James de Boer asked on October 28, 2025 17:47

I have a marketing automation that is using some custom actions. The code in the custom actions used SiteContext.CurrentSiteID and this worked. We added a wait action into the marketing automation flow before the custom action and the SiteContext.CurrentSiteID seems to no longer contain the site.

Is this expected behaviour and what's the recommended work around?

Recent Answers

Juraj Ondrus answered on October 29, 2025 07:43

The SiteContext and the site ID are usually available within the context of a request. So, I guess that the wait step is long enough for the request to be lost/closed and thus no context is available. You may need to store the value into some persisting storage or use different way of getting the site ID you need, based on some other object info.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.