Skip to main content
Question

Decelerator with tweeter

  • April 5, 2018
  • 3 replies
  • 36 views
B
Forum|alt.badge.img

I am trying to make 1 tweet per hour with Tweeter using Decelerator, but I get this error with every second tweet:

2018-04-05 20:32:30| 16.8| 7.4|ERROR |HTTP/FTP transfer error: 'Timeout was reached'

 

2018-04-05 20:32:30| 16.8| 0.0|ERROR |Please ensure that your network connection is properly set up

 

2018-04-05 20:32:30| 16.8| 0.0|ERROR |No proxy settings have been entered. If you require a proxy to access external URLs, please ensure the appropriate information has been entered

 

2018-04-05 20:32:30| 16.8| 0.0|INFORM|Updating access token for 'sami Google Gmail'
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

danilo_fme
Celebrity
Forum|alt.badge.img+51
  • danilo_fmeCelebrity
  • Celebrity
  • 2077 replies
  • April 6, 2018

Hi @bazooka,

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

Is your Workspace similar?

Thanks,

Danilo

Partner Solutial Brazil - www.solutial.com.br
B
Forum|alt.badge.img
  • bazooka
  • Author
  • 20 replies
  • April 9, 2018

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.

redgeographics
Celebrity
Forum|alt.badge.img+60
  • redgeographicsCelebrity
  • Celebrity
  • 3703 replies
  • April 9, 2018

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.

FME rocks! \m/

Community Stats

32,087
Posts
121,852
Replies
39,729
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.