OAuth v2.0 failed to get the correct session and threw INVALID_SESSION_ID after being idle. Messages are not lost because the time intervals are calculated based on the first time this operation is called and because the API disregards the seconds value. This was fixed so that when two or more subsequent calls occur in less than a minute, each call after the first returns an empty array to avoid duplicates. See the Arguments section in the Salesforce getUpdated operation. This was caused by the Salesforce API ignoring the seconds value for the API’s startDate and endDate fields. The Get Updated Objects operation did not return updated records. To enable this functionality the property has to be set as a VM argument. This issue has been fixed by changing the HTTP client to the one in the Mule SDK. (SE-13470)Ĭalls to the Salesforce Create Job Bulk v2 operation with a large volume of data caused : Java heap space error. The Java module was removed from the Salesforce Connector dependencies. Salesforce Connector relied on an outdated version of the Java module that caused compatibility issues with other modules. In version 9.7.10, a fix for this issue was provided but there was a NullPointerException occurring when the keep alive feature parameters were empty. When a cached connection type was used, the reconnection caused a running source to fail. Salesforce disconnects after a few hours. Upgraded the Object Store dependency to the latest version. Updated File connector dependency for the Salesforce connector to the latest version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |