Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task Flow Steps Do Not Continue. #3340

Open
issue-tracker bot opened this issue Feb 16, 2024 · 0 comments
Open

Task Flow Steps Do Not Continue. #3340

issue-tracker bot opened this issue Feb 16, 2024 · 0 comments
Labels
priority/high high priority issues type/bug an issue describing a problem

Comments

@issue-tracker
Copy link

issue-tracker bot commented Feb 16, 2024

Requested By: Alex DeBirk ([email protected])

Priority: High

Version: 3.8.0

We are having a problem getting task flows to flow. We have a report with three steps and 3-7 tasks within each step. We initiate the task through a macro button. We have the "Complete All" box checked. After clicking the macro button, the seven tasks in the first button execute as expected (two phone calls, two damage teams, one damage cargo transfer, one security evacuation). We then complete all tasks and verify them at the Core station. However, the next task flow step fails to trigger. Some steps have macros that fire upon completion after a delay, and at first we thought maybe we just have to wait for those macros to finish, but no, the second step never triggers. This also happened when we deselected "Complete All." We have started new flights, reset the server and the computer, all sorts of things to see if we could get this to work, to no avail.

Steps to Reproduce

  1. Create a task flow.
  2. Create two steps in the task flow.
  3. In the first step, create more than one task.
  4. Give the first task inside the first step a macro of an inter-ship message and a 30 second delay.
  5. Check complete all box.
  6. Create a task in the second step.
  7. Trigger the task with a macro button.
  8. Complete all steps inside Step 1 and verify them. Let the delay play out.
  9. See if the second step triggers.
@issue-tracker issue-tracker bot added priority/high high priority issues type/bug an issue describing a problem labels Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/high high priority issues type/bug an issue describing a problem
Projects
None yet
Development

No branches or pull requests

0 participants