For example, most every setting supported by both engines uses the same config, but event gateways were an example where the two vendors had such different implementations, CFConfig stores adobe EGs and Lucee EGs separetely and doesn't try to find any common ground.

It doesn't "cause any issues" per se, but it does make it a little more annoying, lol

Just update to the latest version of CFConfig

THere is a lot of overlap with Adobe's scheduled tasks so it uses the same JSON struct and can even import most data between engines

The

cfconfig task list
cfconfig task save
cfconfig task delete

also work

The one trick is that scheduled tasks go in the web context. If you run any of the

cfconfig task

commands above, they will default to the

luceeWeb

format.

But if you're doing a JSON import, you'd need to manually import it into the web context

cfconfig import from=settings.json toFormat=luceeweb

Or you can use any of the file-name conventions such as having a

.cfconfig-web.json

file that will auto import into the web context

Or the

cfconfigweb

env var https://cfconfig.ortusbooks.com/using-the-cli/commandbox-server-interceptors/server-start#environment-variable

Or the

cfconfig.web

key in your

server.json

https://cfconfig.ortusbooks.com/using-the-cli/commandbox-server-interceptors/server-start#server.json-properties

There's a lot of ways to do it 🙂

You can also use the

--pauseTasks

flag to

cfconfig import

or the equivalent

cfconfig.pauseTasks

key in the

server.json

if you want to import the tasks as paused when setting up a server.

Are you in the right directory?

Also, try

cfconfig task list

And you installed the latest CFConfig too, right?

update --system

I did a

install

let me do an update

❯ cfconfig show fromFormat=luceeWeb { "adminSalt":"773ED510-8029-40D9-A280F5F0298CF98F", "componentPaths":{ "xampleComponentPath":{ "inspectTemplate":"Never", "name":"xampleComponentPath", "physical":"/some/Component/Path", "primary":"Resource" } }, "hspw":"0e2f0d33e5f0f0a7fb3f957b84668d83f9f69516be96aca5f5867c8d268be96c", "loggers":{ "application":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/application.log" }, "layout":"classic", "level":"info" }, "exception":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/exception.log" }, "layout":"classic", "level":"info" }, "mail":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/mail.log" }, "layout":"classic" }, "remoteclient":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/remoteclient.log" }, "layout":"classic", "level":"info" }, "requesttimeout":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/requesttimeout.log" }, "layout":"classic" }, "scheduler":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/scheduler.log" }, "layout":"classic" }, "trace":{ "appender":"resource", "appenderArguments":{ "path":"{lucee-config}/logs/trace.log" }, "layout":"classic" } } }

Have you restarted the CLI since you updated?

❯ cfconfig task list Task: every-month URL: http://localhost:80/?program=once Interval: Monthly Status: Running

So you were still on the old version basically as far as what was loaded in memory of the CLI

thanks, I'll continue on this side and test some more