How to handle errors when multiple flows are running, Skip the failed flow and resume flow execution?
I need to skip the failed flow and continue the rest part for execution
In the PAF(pace automation Framework)we have a feature to do this .
If we put the flow in init separated by comma, it will automatically skip the failed one and continue execution.
Related
What happens to a failed Service Task when the application is restarted. Will it attempt to retry the Service task once again.
If not, how does the Process proceed. Is there a way to manually retry the Service task ?
I could see from Flowable API, that taskQuery lists only the UserTasks.
In Flowable when an execution fail (due to some exception), the transaction would be rollbacked to the previous wait state in your workflow. This means that the next time it runs it would continue from there.
You can make a Service Task async which would make it a wait state. In that case an Async Job would be created and that would be retried (by default 3 times, but that is configurable). If the Service Task fails all the time (the configured number of retries) the job would be moved into the dead letter job and then you need to manually trigger it.
In drone you can detach steps as seen here: https://docs.drone.io/config/pipeline/steps/
Example use case:
I started a detached database. Some tests run against it. Then the db is no longer needed so I would like to terminate that detached step.
I don't think one can do that in Drone. As mentioned in the service docs, detached steps are basically services. And also mentioned in the docs is:
It is important to note the service container exit code is ignored, and a non-zero exit code does not fail the overall pipeline. Drone expects service containers to exit with a non-zero exit code, since they often need to be killed after the pipeline completes.
So Drone doesn't care about services after they are started and as far as I know doesn't give us any options to stop them. But they will be automatically killed when all the steps are finished.
If you are trying to run two types of test in a single build and require different resources for each, I'll suggest look into multiple pipelines and create separate pipelines for them instead of starting/stopping services.
I am writing a SCDF spi implementation for supporting stream and task application. As part of this we need to perform some clean up operations once the task finishes.
Could someone provide info on whether SCDF will be getting a callback on task completion. If not then what are the alternative ways to perform cleanup.
A Task is a short-lived and finite operation. Depending on what you're trying to accomplish, you can do one of the following to invoke any custom cleanup routine.
1) A task running a batch-job and in that job, you can define "n" number of steps as part of a workflow, and upon successful upstream steps, the last step could invoke the cleanup routine.
2) You can have a stream in SCDF listening to Task-complete events (a batch-job example here), which can finally kickoff another task/job to invoke the cleanup routine.
3) You can define a composed-task graph (via Dashboard/shell) where each of the steps (aka tasks) can run its intended operation, and upon successful transition or failure event, you get the opportunity to kick off the cleanup routine.
I am completely new to Spring and Activiti, and made myself a little Project which works just fine. there are 4 service tasks, a REST controller, 1 process, 1 service and 4 methods in this service.
When i call the server endpoint, i start my process and it just goes step by step through my service tasks and calls service.method as defined in the expression ${service.myMethod()}.
BUT, what i really need is a workflow that stops after a servicecall and waits till there is another request sent, similar to a user task waiting for input, the whole process should pause till i send a request to another endpoint.
like myurl:8080/startprocess, and maybe the next day myurl:8080/continueprocess. Maybe even save some data for continued use.
is there a simple predefined way to do this?
Best regards
You can use human tasks for that or use a "signal intermediate catching event" (see activiti´s user guide) after each ativity.
When you do that, the first rest call will start a new process instance that will execute your flow´s activities until it reaches a the signal element. When this happens, the engine saves its current state and returns control to the caller.
In order to make you flow progress, you have to send it a "signal", something you can do with an API call or using the rest API (see item 15.6.2 in the guide)
I've implemented a BeanShell listener in my Jmeter test plan which I use to run a script that sends information after each request into Splunk. However, I'd now like to be able to generate a similar message at the end of each Thread run, regardless of whether or not there was an error in its execution.
At present when an error occurs I start the next thread. I'd like at this stage to be run another BeanShell script where I can collect and send summary inforation for that thread into Splunk before it starts the next Thread. Is this possible?
Your option is to code a class implementing ThreadListener:
http://jmeter.apache.org/api/org/apache/jmeter/testelement/ThreadListener.html
See also this:
http://jmeter.apache.org/extending/jmeter_tutorial.pdf