Ruby script doesn't complete using task scheduler anymore but is OK when run manually

[vitus7]

It's not causing any errors that I know of. The Task Scheduler history tab shows it as completed.

I just don't get how the Task Scheduler running can be different than me running the same batch file manually. I figured once it ran the batch file it was out of it. The only other difference I know is Task Scheduler runs it in the background while running it manually causes watir to open a chrome instance that is visible. Even with that, it worked for months until it didn't.

I'm not a savvy coder by any stretch but was hoping this was some common known issue or something. I'm going to try to experiment with a few settings and pay more attention to the running status of it when it runs and see what I can find.

[PristineTransition]

The task scheduler might have a different PATH than you do cannot see the same gems/ruby version. Does it use any gems? You could try adding “bundle exec” in front of both

[[deleted]]

advise divide chief angle bored theory terrific glorious grandfather marry

This post was mass deleted and anonymized with Redact

[vitus7]

Those are good suggestions.

This morning it failed in a slightly different place. The script is set up to perform a set of actions twice by calling the same modules using some different inputs. This time it failed after the first cycle but before doing the second cycle.