Timeline for Runtime error in Marketing Cloud Automation
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2021 at 0:18 | vote | accept | Duc Le | ||
| Oct 8, 2021 at 11:47 | comment | added | Gortonington | Also as an alternative, what I do instead of calling multiple automation is make the script activity run for ~25 minute via a do/while loop and then have two inside an automation scheduled to run hourly. I then add a sql query and validation step before it to stop the auto if there is no more data to process. This removes the risk of the API call to start the next automation failing and adds a break point to stop needless processing. | |
| Oct 8, 2021 at 8:26 | comment | added | Jonas Lamberty | click the link in my post, I referenced the source for calling an automation through api and also had more details about batching. 10000 records was just a random anecdote (they are the SF Bulk API record limit) , that has nothing to do with WSProxy or SSJS. I do not think that wsproxy is anymore promising, give or take a few seconds or rows processed. If your script runs 30 minutes, you have a more fundamental problem than the ssjs / wsproxy choice. | |
| Oct 8, 2021 at 7:58 | comment | added | Duc Le | Great post, Jonas! My main data was from an SQL query. I don't think my data will be up to 10000 records so may be WSProxy seems like a promising solution. As I understand, I may need to segment my main data extension to smaller ones in order to use them in connected automations, right? Basically, there's a script (SSJS?) where it can be able to call automation from there? Can you refer me the source where I can read about connecting up Automations? I am not aware I know about it | |
| Oct 8, 2021 at 6:59 | history | answered | Jonas Lamberty | CC BY-SA 4.0 |