Salesforce streaming API stops streaming after an interval

[RanajitSamanta]

NodeJS =>JSForce current version 1.9.1 has been used for our development.

Problem Statement : After a subscription to the Salesforce streaming API (Email Update)topic, it's stopping continuous streaming sometimes after 10 mins, sometimes after 40-45 mins, checked JsForce documentation as well nowhere has been mentioned any timeout is required to pass as they said only below piece of code will work.

conn.streaming.topic("").subscribe(function(message) {
console.log('Event Type : ' + message.event.type);
console.log('Event Created : ' + message.event.createdDate);
console.log('Object Id : ' + message.sobject.Id);
});
Checked with JAVA client => it's working continuously without stopping and receiving streaming data as well over a period of time without any issue.
Please help us to rectify it with JSForce library.How to do that continuous streaming?

[RanajitSamanta]

@stomita => Please have a look once and try to reply us as it's important for us.

[jan-goebel-lendico]

@RanajitSamanta have you already found a solution / workaround for this?

[RanajitSamanta]

@jangobel : I am subscribing streaming topic every 20 min to keep it alive as a workaround but I found multiple subscription is happening due to this.Still I am wondering if I could get a better solution of it.

[jan-goebel-lendico]

Do you use the SOAP login API or OAuth?
https://jsforce.github.io/document/#connection

[RanajitSamanta]

@jangobel : Yes, we are using below mechanism,
var jsforce = require('jsforce');
var conn = new jsforce.Connection({
instanceUrl : '<your Salesforce server URL (e.g. https://na1.salesforce.com) is here>',
accessToken : ''
});

Actual Code =>
if (this._tokenWithUrl == null) {
this._tokenWithUrl = await this._salesforceClient.getTokenWithURL(Logger);
}
if (this._conn == null) {
this._conn = new jsforce.Connection({
instanceUrl: this._tokenWithUrl.url,
accessToken: this._tokenWithUrl.token
});
}
Token is alive that we have also checked by fetching continuous data from Salesforce using SOQL query and we didn't face any disconnection only streaming is stopped after sometime automatically.Please let us know if you have any workaround.

[asjadsaboor-10p]

I am also facing same issue.

[kindohm]

Have the same issue. Streaming from PushTopic works for a while, then just stops. App is still alive but the streaming connection just seems to die.

[schulace]

I'm pretty sure it has to do with the oauth access token expiring. If the connections access token is expired / invalid, then the streaming will silently fail. So what's likely happening in these cases is that the token expires and then the stream just shuts off. The way to get around this would be to use the refresh token to get a new connection once this happens, but I haven't yet found a way to tell when the streaming API stops receiving data and terminates the connection. Unfortunately, the documentation is wrong, and says "If a refresh token is provided in the constructor, the connection will automatically refresh the access token when it has expired." This is definitely NOT the case right now for the streaming API, and I hope the jsForce devs either create a workaround or write the library to do what the documentation says it does.

[kindohm]

currently working around this by doing the following on a setInterval:

• unsubscribing from topic (topic.unusbscribe())
• logging out (connection.logout())
• log in
• subscribe to topic

The app now seems to respond to streaming events for its entire lifetime.

[rakeshsm91]

@kindohm I have tried the same steps that you have mentioned for keeping the streaming alive. But while testing, I see that I dont receive any messages after the logout, login and subscription.

Is there anything that I should be aware of while subscribing back.

[rakeshsm91]

@stomita Kindly, let me know if you have a better approach to keep the streaming alive.

[stomita]

The automatic session refreshing using refresh token is supposed to use usual REST API clients. Currently the jsforce's streaming doesn't support this. I'm not sure there is a way for streaming connection to swap its authorization token without loosing current connection, should be investigated.

[rakeshsm91]

Thanks @stomita, I tried with new connection at setInterval. Seems to be working.

[rakeshsm91]

@stomita So I tried new connection at setInterval of 20mins, But many times I am seeing the streaming stopping before 20mins. It varies every-time, Sometimes it is 10mins, sometimes 15mins. Any Idea how to debug whats happening. The oath token is still valid during all these.

[rakeshsm91]

@stomita Kindly let us know if you are planning to fix this issue in your next release.