Anyone have any other tricks to prevent a workflow...
# suiteflowe
ehcanadian
05/03/2023, 1:44 PMAnyone have any other tricks to prevent a workflow from initiating besides setting it to Not Initiating and marking it inactive? One would think that would be enough...
k
KevinJ of Kansas
05/03/2023, 1:49 PMJust because a workflow isn't initiating doesn't mean it stops running on records that are already in it.
s
scottvonduhn
05/03/2023, 1:49 PMif you own it, delete it. can’t run if it doesn’t exist. For workflows from a third party bundle, though, I think Not Initiating is the best you can do.
k
KevinJ of Kansas
05/03/2023, 1:50 PMYou can make the record exit the workflow as an administrator.
KevinJ of Kansas
05/03/2023, 1:51 PMSuspended
No new instances of the workflow are created and no existing instances of the workflow are executed.
If the workflow includes scheduled workflows, transitions, or actions, none of them will be executed.
It is not possible to initiate a suspended workflow from SuiteScript, or by using the Initiate Workflow or Mass Update actions in SuiteFlow.
To resume a suspended workflow, change the Release Status of the workflow to a different release status than Suspended.
Use when you want a workflow to stop executing but you do not want to delete the workflow.
KevinJ of Kansas
05/03/2023, 1:52 PMYou probably want a status of "suspended" not "not initiating"
e
ehcanadian
05/03/2023, 1:52 PMThey're newly created OPs that are using the workflow. I can't delete it; dependent records. It's becoming frustrating
ehcanadian
05/03/2023, 1:52 PMYeah, worth trying. One would think being Inactive would be enough though
k
KevinJ of Kansas
05/03/2023, 1:52 PMDid you bundle the workflow over?
e
ehcanadian
05/03/2023, 1:53 PMFrom SB to Prod and then a refresh, yes
k
KevinJ of Kansas
05/03/2023, 1:53 PMIs it possible the workflow is tied to two bundles?
KevinJ of Kansas
05/03/2023, 1:53 PMAlso - is it happening for anyone other than you?
e
ehcanadian
05/03/2023, 1:53 PMYes, it's happening for two of us who are testing
k
KevinJ of Kansas
05/03/2023, 1:54 PMOoof. Sounds like maybe that's a support ticket to NS then.
KevinJ of Kansas
05/03/2023, 1:54 PMOr... do you have a script or another workflow that's potentially that's causing the records to enter the workflow?
e
ehcanadian
05/03/2023, 1:55 PMHrm, possibly. If that's the case and the script doesn't error I'd be surprised
ehcanadian
05/03/2023, 1:55 PMwell, not really, being NS
k
KevinJ of Kansas
05/03/2023, 1:56 PMwell, if you set it to suspended, and it tries to initiate, you'd likely get the error
c
CD
05/03/2023, 2:12 PMYou can always do a mass update to cancel all existing instances of the workflow
e
ehcanadian
05/03/2023, 2:13 PMNice, I'll keep that in mind
c
CD
05/03/2023, 2:29 PMIt's often overlooked that workflows take a copy of the backend code when they are instantiated, so you end up with different versions of workflow instances all over the place.
k
KevinJ of Kansas
05/03/2023, 2:37 PMIt is often worse when you've bundled the same workflow twice - and it has two bundles associated with it. You wind up with duplicate states and then things aren't doing what they should
j
Jono
05/10/2023, 7:19 AMi've added a time in the criteria when schedulling a cutover for a workflow before - i don't recall it giving me too much grief
2 Views