Skip to main content
Question

FME Flow 2023: Schedule running an outdated version of an updated workspace

  • April 7, 2026
  • 2 replies
  • 46 views

bgeorges
Contributor
Forum|alt.badge.img+6

Hello,

I believe I’ve encountered a bug in FME Flow 2023 and would like to know if others have experienced something similar.

I recently updated a workspace by changing the recipients in an email transformer and overwriting the file on FME Flow. This workspace is triggered by two separate schedules: one for Mondays and one for Thursdays. Both schedules are identical except for the day they run.

Surprisingly, when the Thursday schedule ran, the email was sent to the old recipients (prior to the update). However, when the Monday schedule ran, it correctly used the updated recipients.

I have verified the following:

  • The logs confirm that both schedules are calling the exact same workspace file in C:\FMEFlowShare\repositories.
  • I manually checked the workspace on the server, and the parameters are definitely correct.

Why would one schedule seemingly use a cached or "ghost" version of the workspace while the other uses the updated version? Has anyone seen this behavior before?

2 replies

nielsgerrits
VIP
Forum|alt.badge.img+66

Were the recipients originally set by a public parameter? Because the public parameter might be set in the original schedule?


s.jager
Influencer
Forum|alt.badge.img+23
  • Influencer
  • April 8, 2026

Because the public parameter might be set in the original schedule

That has caught me out as well a couple of times...