| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Project-level pipeline execution: Before this release, tasks stored in a Project Space could execute pipelines in a different Project Space or by requests from a different Org. With the current release, tasks must belong to the same Project Space as the pipeline to execute successfully. Learn more.
The Snaplex configuration file (.
slpropz) is no longer available as a URL in the user interface to enhance security. Instead, you can download it from the Snaplex > Downloads tab by clicking
or with the API GET /api/1/rest/plex/config/<path_to_groundplex>. Learn more.
...
Known Issues
When you call a Triggered Task on a Groundplex using the Cloud URL with a payload of 26 MB or larger, the pipeline processing can exceed the WebSocket connection timeout.
While the pipeline succeeds in delivering the payload, the bytes after the 26MB limit might be lost on the response side.
If the payload is on the request side, then only the first 26 MB of bytes are sent to the pipeline, causing the possibility of pipeline failure.
Snaps
The Snaps mentioned in this section are deployed on the Latest distribution type. To access the updated Snap Packs, an Org admin must select the Snap Pack version in Manager > Snap Packs.
...
Some error messages will now include the data type, for example:
Old:
"...where (badId = 1) was aborted:..."New:
"...where (badId = ('1'::numeric)) was aborted:..."
There are some minor text changes to a few of the error messages, for example:
Old:
"Hint: No operator matches the given name and argument types."New:
"Hint: No operator matches the given name and argument type(s)."
...