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.

Sign up for GitHub

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

Jump to bottom

Deleting automation and publishing app did not remove automation from test production environment #7865

Closed
melohagan opened this issue Sep 21, 2022 · 1 comment
Closed

Deleting automation and publishing app did not remove automation from test production environment #7865

melohagan opened this issue Sep 21, 2022 · 1 comment
Assignees
@mike12345567
Labels
bb-automations Budibase Automations related work bug Something isn't working env - test Bug found in test env

Comments

@melohagan
Copy link
Collaborator

Hosting

  • Self
    • Method: yarn dev
    • Budibase Version: 1.4.3-alpha2
    • App Version: 1.4.3-alpha2

Describe the bug
Publishing a cron job automation that prints a log cannot be removed when testing in the dev environment, even after publishing.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new automation with trigger Cron job every minute and connect a Backend log with a message Delete Me
  2. Publish the app
  3. See that the log is printing to the terminal
  4. Delete the automation and publish the app
  5. See that the log is still being printed to the terminal on the cron cycle

Expected behavior
When testing locally, deleting an automation should be reflected upon publishing the app.

Screenshots
Screenshot 2022-09-21 at 09 46 15

Screenshot 2022-09-21 at 09 46 27

Screenshot 2022-09-21 at 09 46 57

Screenshot 2022-09-21 at 09 47 12

It says I have 7 automations
Screenshot 2022-09-21 at 09 47 38

But I have 5...
Screenshot 2022-09-21 at 09 48 08

Cron jobs still running
Screenshot 2022-09-21 at 09 48 28

App Export
Automation History Example-export-1663750127781.txt

Desktop (please complete the following information):

  • OS: macOS
@melohagan melohagan added bug Something isn't working env - test Bug found in test env labels Sep 21, 2022
@melohagan melohagan mentioned this issue Sep 21, 2022
Open
@stale
Copy link

stale bot commented Nov 22, 2022

This issue has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the stale label Nov 22, 2022
@stale stale bot removed the stale label Nov 28, 2022
@shogunpurple shogunpurple added the bb-automations Budibase Automations related work label Nov 28, 2022
@mike12345567 mike12345567 self-assigned this Dec 7, 2022
mike12345567 added a commit that referenced this issue Dec 7, 2022
@mike12345567
Fix for #7865 - if you deleted a cron automation immediately after cr…
bffb414 
…eating/publishing it there was a scenario where prod automations would be out of sync with dev automations and it wouldn't really delete. To get around this, we do an automation sync back to dev DB - meaning that the cron ID is known and can be disabled.
@mike12345567 mike12345567 mentioned this issue Dec 7, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mike12345567 mike12345567

Labels
bb-automations Budibase Automations related work bug Something isn't working env - test Bug found in test env
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mike12345567 @shogunpurple @melohagan