Recently active topics

When a File Arrival job reaches it end time and no file was found, its ends with an exit code 1 and a failed status.Sometimes, not finding a file is normal and you may want to manage this possibility and avoid your job ending as failed. However, exit code 1 is used not only for this special case but also for another reason that makes it a bit more difficult to just simply use the advanced failure criteria of your job.According to the documentation, the exit code 1 is not only returned for a file not found, more information below:"The file was not found. Reasons include an invalid filename, the file has not arrived yet, or permissions."This is also true for UNIX and IBM i file arrival jobs.How to manage this?Let's take an example, below my File Arrival definition:The job end time is 11:00 PM.The next step is to set an event to mark the job as Finished OK if the exit code is equal to 1 AND if the system time is superior to the end time of the job:The complex expression used:[[$JOB TERMIN

Our first in the OpCon Continuum Webinar Series, shows you what it actually looks like to build a workflow in Continuum, and why it feels fundamentally different from what you’re used to.On Wednesday, August 12th, 2026, at 12 PM CT, Bruce Jernell, Solutions Engineer at Continuous, walked us through the redesigned workflow experience.Topics included:How the new single-page workflow designer keeps you in context from start to finish A completely reimagined frequency builder that reads like a calendar, not a code Auto-save and the JSON/code view so you never lose work-in-progress and can clone workflows in seconds Canvas improvements that make building and reviewing dependencies faster and more visual 

In our second session of the OpCon Continuum Webinar Series, we showed how Continuum puts you in control of what reaches production, and gives you the ability to see exactly what a workflow will do before it ever runs.On Wednesday, August 26th, 2026, at 12 PM CT, Bruce Jernell, Solutions Engineer at Continuous, walked through versioning, deployment, and forecast mode.Topics included:How workflow versioning works in Continuum — and why being able to go back to any prior version changes the way you work A new deployment flow that lets you target specific environments, set a go-live time, and choose exactly which version your teams get Forecast mode: previewing the shape of a workflow on any future date before a single build runs How the same versioning and deployment controls apply to self-service buttons, not just workflowsWhether you manage one environment or several, this session shows you what it looks like to push to production on purpose.   

The New Workflow DesignerOpCon Continuum brings the entire workflow-building experience into one place. Instead of moving from screen to screen, you work on a single responsive canvas with all of your settings docked on the right — name the workflow, choose a workspace, set your options, and save a draft without ever leaving the page. Terminology has been standardized along the way, so what you may have known as Schedule Master or Studio is now simply Workflows, and departments are workspaces. Watch Bruce build a workflow from scratch in the new designer. 

Versioning & DeploymentChange control for workflows is no longer a separate application. The capabilities customers valued in OpCon Deploy — versioning, controlled promotion between environments, and transformation rules — are now built directly into OpCon Continuum.Workflows live in the database as a draft until you commit them as a version Every saved version records the user and the notes describing what changed Deploying is a separate, deliberate step through Manage Deployment, where you choose which version goes to which environment Set the rule to "latest" and each committed version deploys automatically Transformation rules swap agents and values as a workflow moves between environments Effective and expiration dates let a deployment take effect on a specific date or run only during certain months Auto-build continues to work as it does today, respecting your override settingsWatch Bruce commit a version and deploy it. 

Calendar-Style Frequency BuilderFrequencies now live in their own dedicated area of the toolkit rather than being created on and tied to individual jobs. That means a frequency continues to exist even if no job is using it — no more losing a frequency because it was removed from the last job that referenced it.How frequencies work hasn't fundamentally changed, but how you build them has been simplified:A calendar-style builder that follows the same patterns you already use when scheduling in Outlook or a personal calendar — choose how often to repeat, then refine from there A live forecast for that specific frequency, visible as you work, so you can confirm the dates before you save The option to layer in a specific calendar for additional datesWatch Bruce walk through the new frequency builder. 

Code ViewCode View exposes the JSON structure behind a workflow, giving you a direct window into every job it contains. If you know scripting, you'll recognize it immediately. If you don't, it's still useful:Ctrl+F searches across the entire workflow and takes you straight to each match Find-and-replace applies the same change across many jobs in one pass The JSON can be copied out or exported for use elsewhere, and pasting it back in applies your changes It's a fast way to bring older workflows up to standard, or to add a large number of jobs at onceWatch Bruce use Code View to search, edit, and document a workflow. 

The SAM log is the most important log in OpCon. SAM, or Schedule Activity Monitor, is the central process that runs the automation engine. It handles scheduling, communicates with agents, processes events, and manages jobs. Because SAM touches everything, its log is the most comprehensive source of information when something goes wrong.What the SAM Log ContainsThe SAM log records all successful processing information from the SAM process, including:Schedule and job starts and completions OpCon event processing, from any source (Self Service, Notification Manager, job triggers, messaging) Configuration information when SAM starts up or regenerates Agent communication summariesHow to Read the SAM LogThe SAM log is written top-down, with the most recent entries at the bottom. When troubleshooting a specific event or failure, scrolling to the bottom is usually the fastest approach, especially if you can reproduce the issue and then immediately check the log.A Note on SAM Log LockingIf the