Skip to main content
C
CHASEONHO18-Opal
18-Opal
February 1, 2018
Solved

Stream Thing service issue(update, add)

  • February 1, 2018
  • 1 reply
  • 2647 views

I have newly configured the update service during the stream's service.

Given a Thing's name and attributes, it will fetch a specific one-line stream

Then, based on a single line of information, change only some of the values, and then modify the stream with a specific one-line id.

The problem is that services are sometimes delayed.

When I think of it, is it superimposed on the moment the source changes from that user to the superuser and the stream modifications that the subscription does?

Does ThingWorx not immediately modify the stream?

The modification mentioned here means UpdateStreamEntry

In addition, when an entry is added to the stream, the source is set as the connected user

But after a while it turns into SuperUser. Why?

thank

Best answer by CHASEONHO

We suspect that a problem occurs when the UpdateStreamEntry is executed at 10-second intervals in the subscription and the UpdateStreamEntry is executed manually at the same time.

So I added another field to the stream so that the UpdateStreamEntry that runs every 10 seconds in the subscription is done once.

Then, when I manually run the UpdateStreamEntry, I get the result that it is not delayed but it changes immediately.

When anyone tries an UpdateStreamEntry, make sure that it does not overlap with the subscription (which runs the UpdateStreamEntry as a timer). This may seem like the service is not running.

thank

1 reply

C
CHASEONHO18-OpalAuthorAnswer
18-Opal
February 1, 2018

We suspect that a problem occurs when the UpdateStreamEntry is executed at 10-second intervals in the subscription and the UpdateStreamEntry is executed manually at the same time.

So I added another field to the stream so that the UpdateStreamEntry that runs every 10 seconds in the subscription is done once.

Then, when I manually run the UpdateStreamEntry, I get the result that it is not delayed but it changes immediately.

When anyone tries an UpdateStreamEntry, make sure that it does not overlap with the subscription (which runs the UpdateStreamEntry as a timer). This may seem like the service is not running.

thank

Terms & ConditionsAccessibility statement