<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title>Bing: If Condition in Framework as Code Less in En Vision Document Module</title><link>http://www.bing.com:80/search?q=If+Condition+in+Framework+as+Code+Less+in+En+Vision+Document+Module</link><description>Search results</description><image><url>http://www.bing.com:80/s/a/rsslogo.gif</url><title>If Condition in Framework as Code Less in En Vision Document Module</title><link>http://www.bing.com:80/search?q=If+Condition+in+Framework+as+Code+Less+in+En+Vision+Document+Module</link></image><copyright>Copyright © 2026 Microsoft. All rights reserved. These XML results may not be used, reproduced or transmitted in any manner or for any purpose other than rendering Bing results within an RSS aggregator for your personal, non-commercial use. Any other use of these results requires express written permission from Microsoft Corporation. By accessing this web page or using these results in any manner whatsoever, you agree to be bound by the foregoing restrictions.</copyright><item><title>Job stuck in loop condition due to NotRunning (Job) condition | AutoSys ...</title><link>https://community.broadcom.com/question/job-stuck-in-loop-condition-due-to-notrunningjob-condition</link><description>So we have a Autosys job (let's say JobA) that's stuck in a loop due to the condition NotRunning (jobA). So, the job continuously restarting itself, moving from STARTING state to RUNNING state, completing either in SU or FA &amp; restarting itself.</description><pubDate>Sun, 29 Mar 2026 15:37:00 GMT</pubDate></item><item><title>Autosys job not starting based on starting time but starting based on ...</title><link>https://community.broadcom.com/discussion/autosys-job-not-starting-based-on-starting-time-but-starting-based-on-dependency-job-condition</link><description>1. Autosys job not starting based on starting time but starting based on dependency job condition.</description><pubDate>Thu, 02 Apr 2026 11:01:00 GMT</pubDate></item><item><title>Dependent job not starting after condition met when included under a ...</title><link>https://community.broadcom.com/discussion/dependent-job-not-starting-after-condition-met-when-included-under-a-box-job</link><description>We have created &amp; run other jobs successfully previously with a condition and also setting dependency under a box so that is what makes this so frustrating. We have job B with condition S (job A). When both of them defined with a box_name parameter (both under the same BOX job), then even after successful run of job A, job B does not start.</description><pubDate>Sat, 28 Mar 2026 15:31:00 GMT</pubDate></item><item><title>when to use look back condition in autosys | AutoSys ... - Broadcom</title><link>https://community.broadcom.com/discussion/when-to-use-look-back-condition-in-autosys</link><description>When i am studying the look back condition, its taking the last instance run of the condition or predecessor job.Just want to know when to use this look back co</description><pubDate>Thu, 02 Apr 2026 00:02:00 GMT</pubDate></item><item><title>Difference between status, condition, Operstatus and Admin status in ...</title><link>https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?MessageKey=0532e11f-ab75-4ee4-bac6-027e5e565ec8&amp;CommunityKey=671164c3-e575-4b08-96ab-edc2e1ceed13&amp;tab=digestviewer</link><description>1. Difference between status, condition, Operstatus and Admin status in the component details of the interface in spectrum.</description><pubDate>Thu, 02 Apr 2026 14:14:00 GMT</pubDate></item><item><title>Does the MAX TASK condition issue a message when you hit MAX TASKS? | IDMS</title><link>https://community.broadcom.com/mainframesoftware/communities/all-discussions/viewthread?GroupId=1969&amp;MID=825067&amp;CommunityKey=b1472505-bd98-47a6-aed7-a494d48fc3ab</link><description>What they want is a message to be issued when a max task condition is encountered so that automation can send out warnings and E-mails to all the appropriate parties.</description><pubDate>Tue, 31 Mar 2026 17:29:00 GMT</pubDate></item><item><title>How To Skip one job in workflow if previous job has already ... - Broadcom</title><link>https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=780675</link><description>As Jeroen said , I am using workflow variable to pass condition to another. And we have another issue in v10 build 312 , SYS_ACT_PREV_NR can detect previous job's runid correctly but neither GET_UC_OBJECT_STATUS nor GET_STATISTIC_DETAIL can get job's status correctly.</description><pubDate>Fri, 27 Mar 2026 19:00:00 GMT</pubDate></item><item><title>Need to use a wildcard in a condition with if job is running | Automic ...</title><link>https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewquestion?ContributedContentKey=5143d94f-2f45-4258-84ac-b71d290a19c6&amp;CommunityKey=2e1b01c9-f310-4635-829f-aead2f6587c4</link><description>I need to use a wildcard in a condition on if job is running. Since the condition uses the alias name instead of the job name I need to be able to have the con</description><pubDate>Sun, 29 Mar 2026 04:32:00 GMT</pubDate></item><item><title>Where could I find the syntax and explanation for "condition ... - Broadcom</title><link>https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=750754</link><description>Where could I find the syntax and explanation for "condition" attribute of a job? I have seen samples like : condition: s (job_name, 0). I want details on this and other attributes and syntax for the JIL.</description><pubDate>Tue, 31 Mar 2026 22:09:00 GMT</pubDate></item><item><title>Using notrunning condition causes a loop | AutoSys Workload ... - Broadcom</title><link>https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=782017</link><description>Using notrunning condition causes a loop L.LEONG Dec 20, 2017 07:19 PM I have a a jobs which cannot run concurrently. My problem is that once the success conditions are met, ... You might want to add a look-back to the success () condition. For example: Job: LRST-dist-reptmart-wrapup-clearing-fact01-load-etl-00d ...</description><pubDate>Mon, 30 Mar 2026 04:38:00 GMT</pubDate></item></channel></rss>