Hi @bazooka,

I maked a example with my Twitter account and the transformer Decelerator without Error.

Is your Workspace similar?

Thanks,

Danilo

My original Workspace includes HTTPcaller. I don't know if it causes some thing. I can't access that Workspace at the moment, but it is like this

There is much more happening in the beginning, but the end is same (Decelerator -> Tweeter)

I am going to try do 2 Workspaces for this task. 1st one reads data from web page and 2nd does Tweets. Those I am going to run with Workspacerunner. I hope that helps.

It does sound like it's a timeout either in the HTTPCaller (if that's being used after the Decelerator) or the Tweeter. Without seeing the entire workspace and log it's hard to give a definite answer though but my guess would be that the connection is opened on either of them and kept open while the workspace is running (and sitting there, doing nothing, for an hour per feature, while still claiming a license)

I think you should look into scheduling tweets via the API.