Forum Discussion
Hi EmEm, so happy to connect with you again. Hope you’re doing well. Salamat kuya for the nice wrapper solution.
My plan next week is to discontinue using my task’s CloudURL and begin using the SecuredURL that points to our groundplex snaplex. I believe by doing this, I can resolve the issue of being limited to 10 concurrently running tasks. Based on what I’ve been reading, I shouldn’t have concurrency limitations when I’m running on the groundplex. Do you have any experience using this method?
If this method works, that will be great. I’d like to see if this works before introducing ultra pipeline tasks. We’re not using those right now so I’d probably have to present a really good use case for it and (maybe?) the added expense that comes along with it.
I’ll let you know how it goes. Btw, I like your description label. MVP Rock Star!. That’s so cool!
Only when invoking the cloud url of the triggered task has this limitations
No limits when invoking the on-premise url
Hi dmiller,
Thanks for update, still we are facing below issues, please help me on this.
When we are using the as per the document format for attachement, we are not able to attached the file,2 Step: When we are used this file name <<TestingEmail.json>> Its getting the old file, not current file.
Thanks,
kullayappa- rohithmadhavan6 years agoEmployee
@Kullay There’s a race condition in this pipeline design if the File Writer Snap is writing to TestingEmail.json. Since the File Writer and Email Sender Snaps are disconnected, their relative order of execution isn’t guaranteed. I would suggest connecting the File Writer’s output view to the Email Sender’s input view as shown below.
@rohithmadhavan,
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438208/Email+Sender
as per the document, I have followed I am getting current file but it’s getting Empty files also.We are expecting only error time only.
Thanks,
kullayappa