Alan L.

Cloud Triggered Task Starting Multiple Concurrent Executions Despite Concurrency Setting Has anyone seen a Cloud Triggered Task ignore the "Do not start a new execution if one is already active" setting? I have a task configured as a Triggered Task with that option enabled. My current environment only has a single Ultra Snaplex available, However, I observed three executions of the same task start within ~1 second of each other and run concurrently for about 11 minutes. My expectation was that only one execution of the task would be allowed at a time and subsequent trigger requests would be blocked while the first execution was still active.

Any insight would be appreciated.

I need to sign a JWT using an RSA private key (.pem) inside a SnapLogic pipeline to authenticate a REST call via HTTP Client Snap. Planning to use a Script Snap (Python). What's the recommended way to store the PEM securely? Pipeline parameter, SLFS, or another approach? Also, which Python libraries are available in the Script Snap runtime for JWT signing (RS256)?