Scheduled jobs running after cloning

[puchu]

HI Folks,

i am facing one issue where after the instance cloning, the scheduled jobs which are on non production environment and which are inactive, but still they are running.

Due to this, the production may have severe impact.

Please suggest what needs to be checked in such situation.

Thanks in advance.

[Ashutosh Munot1]

Perfect!

So you know which scheduled job are running?

If yes, then you need to Find which schedule import is belongs too.

That scheduled import is true and hence it is triggering data source and that data source have script in which scheduled job is invoked.

Go to scheduled import then in that in related list you may find data sources and then check those data source scripts.

Thank you,
Ashutosh Munot

[puchu]

I found one transform map, if i deactivate it , the scheduled job will still execute?

[puchu]

yes i checked and it is still running

[puchu]

Hi Ashutosh,

There is one business rule"Automation synchronizer"which actually creates a entry in sys_trigger table whn the schedule job is active and removes the entry when schedule job becomes inactive.

So i have written setWorkflow(false) in the clone cleanup script for sysauto table as the business rule is also written on the same table.

Will this work?

[Ashutosh Munot1]

Hi,

When you do this that BR will not trigger. So it should work for you.

Thanks