Skip to main content

Hi, I get warnings when running some automations in FME Flow. Running just the workspaces manually does not give these warnings and all data is written as expected in both cases. Any ideas for what is causing these to appear? Thanks 

Automation log:

1 2024-04-04T22:00:00+02:00 | 803022 : Dependent parameters: :]
2 2024-04-04T22:00:00+02:00 | 803018 : Expected parameters: :DestDataset_GEODATABASE_SDE, SourceDataset_MSSQL_ADO_3]
3 2024-04-04T22:00:00+02:00 | 803019 : Provided parameters: :SourceDataset_MSSQL_ADO_3]
4 2024-04-04T22:00:00+02:00 | 803019 : Provided parameters: :SourceDataset_MSSQL_ADO_5, SourceDataset_MSSQL_ADO_6, SourceDataset_MSSQL_ADO_7]
5 2024-04-04T22:00:00+02:00 | 803022 : Dependent parameters: :]
6 2024-04-04T22:00:00+02:00 | 803018 : Expected parameters: :]
7 2024-04-04T22:00:00+02:00 | 803022 : Dependent parameters: :]
8 2024-04-04T22:00:00+02:00 | 803018 : Expected parameters: :]

Hi @albjoh ,

What version of FME Flow are you using? Is the job still completing successfully with these warning messages?

There was a known issue in FME 2021 where automation logs were logging group box parameters. This was resolved in FME 2021.2+. 

There was also another known issue with FME 2023.0 where there are warning messages in the automation logs that trigger a workspace with dependent parameters. This issue was resolved in FME 2023.1.

 

Hope this helps and gives more context.

Kezia

 


Hi @keziaatsafe 

I’m running FME 2023.1.1.1 on both Flow and Form. Yes, the triggered workspaces completes with success. I have to check again if I missed upgradaing some reader/writer, but they should be up to date too.

Thanks 


Hi @albjoh ,

Thanks for confirming your versions. Then it looks to be related to the second known issue with dependent parameters. Do the automations logging these warning messages contain workspaces that have dependent parameters? Are you able to see a pattern of when these warning messages are logged between your automations?

 

Thanks,

Kezia


Hi @keziaatsafe, I have not yet been able to identify any patterns that differs between an automation that throws the warning and the ones that don´t. It obviously points to the readers/writers database connections parameters but can’t see no difference there so still looking in to it..


Hi!

This could happen when you update workspace and don’t stop and re-run (i.e update) the automation. The input parameters or their names of the workspace may be changed and the automation does not know that. 


Hi @kirken, Yes this seems to be the case. Thanks for your input!


Reply