Unstable deploy UI

I’ve faced two issues lately with the deploy page in Create. Firstly, sometimes when I select now when deploying to test or stage, it creates a scheduled deploy and a deploy that is loading at the same time. The change details sometimes moves as if it is deployed and sometimes not. It always ends up deploying correctly, but it is misleading as you are doing it, it takes long and its confusing.

The second issue that are causing headaches and hearts attacks these last few days is the deploy to production randomly shows that I am deploying, when I have been nowhere near the deploy button. I usually only see it because there is a loading icon on production under Cluster Status. I am not sure if this is an actual deploy that interrupts active users or if it is an UI thing. After the “deploy” is over it shows the correct model as active.

Hello!

Can you check if your device shows the correct time? The deploy page uses the clock on your device to display the correct status, so the issue might be related to that.

If that doesn’t solve the issue, could you provide us with some screenshots or screen recordings of when this happens? Either here or by DM.

I am able to recreate the issue by manually setting the time of my device so that seems very plausible. Do you believe the second issue of deploy is also caused by that? Our model numbers are around 335xxx and the last time the deploy bug occurred the model number was something around 4xxxxx .

It might be, but it’s a bit hard to tell without seeing the behaviour.
Please let us know if it happens again and send a screenshot or screen recording.

I also experienced this issue on Friday, so not necessarily just a local issue. In addition to this it also appeared to be a bit arbitrary what changes were included in the deploy as well (a big quantity of changes were often missing when I tried to deploy, and only appeared after I deployed something else).

Can also add that for me, Friday was extremely unstable in general, and the ampSession error message (Create: Ampsession already has a socket - Bug reports - Appfarm Community) occured at least once every 30 minutes

It has happened again multiple times today. Happens on multiple devices at the same time. The deploy UI suggested the actual deploy took 15+ minutes. Also had an issue yesterday where not all changes were part of the deploy, which seems to be a recurring issue couple times a month (almost always when I’ve deleted something in a view).

There are two minutes between these screenshots.

Thank you for reporting this. The model number, which is also the UNIX timestamp of the deploy suggests that this deploy happened at 08:15 this morning. Is that correct? And did it then show the “Deploying model […]” message for 6 hours before showing “Active deploy (6 hours ago)” as shown in your second screenshot?

The issue you mention with not all changes being deployed sounds very peculiar. Does this happen when deploying all changes or have you also been using Targeted Deploy?

08:15 this morning sounds accurate. It switches between deploying and active deploy. So it said deploying for about 15 minutes initially, then a couple hours later I saw that it was deploying. The six hours later, and it is also currently “deploying” again.

I have only observed it when deploying all changes, but it does not even seem to trigger an event to suggest that there has been changes. When this occurs, which seems a bit random, the changes are not reflected in the change details. So you can’t actually deploy it unless you change something else. Usually I do some combination of duplicate and delete to actually trigger the “changes” to be deployable.

I see, to clarify:

  1. When it switches between “deploying” and “active deploy”, does that affect the client users? Does the deploy go out to the client as usual, even if it switches back and forth in Create?

  2. Once you do the combination of duplicate and delete, do the missing changes show up in the change details?

  3. Do you ever experience changes included in the change details not being applied in the environment you deploy to?

  4. Do you see any pattern in what types of changes are not included in the change details?