I am getting errors while JobHistoryReader

anyone

Hi @asadamjad​ ,

A couple of questions to get started:

• Are you running this workspace on FME Server?
• Do you have a job log for us to look at?
• What version of FME Server are you using?

Thanks,

Kezia

Any updates on this ?

I am now getting this same error, in both Desktop and Server.  It worked fine until 3 days ago, the workspace was not edited.  

FME 2022 Build 22765

2024-9-26 09:44:52 | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

89           2024-9-26 09:44:52 | Feature Type: `JobHistoryReader_LoopHere'

90           2024-9-26 09:44:52 | Attribute(32 bit integer): `Loop to JobHistoryReader_LoopHere1709132937 Input Splitter.BranchingFactory.Count' has value `1'

91           2024-9-26 09:44:52 | Attribute(string: UTF-8) : `_min_job_age' has value `20240925000000'

92           2024-9-26 09:44:52 | Attribute(64 bit integer): `_offset' has value `0'

93           2024-9-26 09:44:52 | Attribute(string: UTF-8) : `fme_feature_type' has value `Creator'

94           2024-9-26 09:44:52 | Attribute(string: UTF-8) : `fme_geometry' has value `fme_undefined'

95           2024-9-26 09:44:52 | Attribute(string: UTF-8) : `fme_type' has value `fme_no_geom'

96           2024-9-26 09:44:52 | Coordinate System: `'

97           2024-9-26 09:44:52 | Geometry Type: IFMENull

98           2024-9-26 09:44:52 | Coordinate Dimension: 2

99           2024-9-26 09:44:52 | ===========================================================================

100        2024-9-26 09:44:52 | Loop to JobHistoryReader_LoopHere1709132937 Input Splitter (BranchingFactory): Transformer/Factory JobHistoryReader_HTTPCaller is blocking and cannot be used in a loop, but was found between 'Loop to JobHistoryReader_LoopHere1709132937 Input Splitter' and 'JobHistoryReader_LoopHere1709132937 Input Splitter'

Hi @mferwerda3 

I found this community post: Dasbhoard workspace JobHistoryStatisticsGathering.fmw Errors after upgrade to FME Server 2022.2.7.

It looks like the solution for that error is to change the maximum number of concurrent HTTP Requests from 25 back to 1.

Please let me know if this works for you, and if it doesn't, I would be happy to look into this further.

Crystal 

Thanks, that worked, much appreciated.