Gardening

Cjb fruit trees bot working

Cjb fruit trees bot working


We are searching data for your request:

Forums and discussions:
Manuals and reference books:
Data from registers:
Wait the end of the search in all databases.
Upon completion, a link will appear to access the found materials.

Cjb fruit trees bot working on one day

I have a bot that runs on windows server 2003 x64 for a large Cjb-fruit tree orchard in the midwest US. I am having issues with the bot stopping and crashing when I try to run the scheduled task. In order to try and get the bot running I added a new scheduled task and ran the bot with no errors and it was able to log in fine. I think it may have something to do with not being able to find the c:usersusernameappdata oaming folder on the server, but I am unsure.

I am using powershell v3 to run the bot and it is currently running as a different user to that of the account I am logged in with.

What is the correct location for the roaming folder? Where do I need to be on the server to be able to successfully run the bot?

You don't need the roaming folder at all. A Cjb-fruit tree bot runs just fine without it. Also, do the following in the PowerShell script:

$env:roaming = [Environment]::GetFolderPath('Roaming')

And it will automatically use the settings in Windows to find the roaming folder.

The bot can run fine if you start it as the same user as you are logged in under. When running as different user, it does not go to C:usersUsernameAppDataRoaming

It seems to run okay, but does not always finish. I would assume that there is an issue on the bot side since it did not crash or time out.

I see no errors on the log page. Should I run the bot manually every few days or should I let the bot run as a scheduled task and then re-run the Bot manually whenever it needs to be run? If I do need to run it manually, how can I run it as a scheduled task?

This Bot is based off the Cjb-Fruit bot that's been in use for over 6 years in our company. It has a variety of fruit trees in a very complex system. The bot is designed to handle a large variety of tree types and growing conditions. As such, it will not always finish running, if it finishes running. We have a variety of workflows set up to handle each of these scenarios. Typically, when the bot takes a long time to complete, the bot sends an email to our internal team that it will not be returning any further results until the next run.

If your issue is a timeout, the bot should be running fine. You can test this by simply doing a search for 'Cjb-fruit' and trying to open a result in the bot (via the bot command). If it times out or fails to open a result, I would first check for:

Are the bot logs (C:UsersusernameAppDataLocalBotBuilderotcache) in sync with your database? This is what I always check first.

Can the bot access the api key in the api settings and successfully get a list of trees and the names of those trees in your data base?

Can the bot open the site? Is there any errors when opening the site? Is it an internal error or an error getting to the site?

Can you test opening and sending emails to support, and seeing if you get an error in those communications?

If there are no errors and the bot is running fine, the first thing I would check next is the bot cache (C:UsersusernameAppDataLocalBotBuilderotcache) and try to delete any cached results. I think this might be why some of your bot results are not opening. Sometimes bot results can be cached as well, so clearing those out might solve the issue.

I think the best thing to do in these situations is create a new bot and test your results again from a new environment. I would go ahead and delete that bot as well to avoid having that environment in your BotBuilder project, as you mentioned that some of your bot results are still failing.

This is what it looks like when you click test on a bot result in BotBuilder

When you click test in BotBuilder, a test bot will pop up. The first thing you should look at in the output pane is the status. If the status is OK, then the bot is running. If the status is NOT OK, then the bot is not running. This can help you isolate what the issue is and where it is occurring.

Are you getting an error message on your bot results?

Are there any errors in the output pane for the bot being tested? If yes, this will help you identify the error. In the screenshot above, you can see that there are two errors. The first error is the "An error occurred. Please try again." error, and the second error is a 500 (Internal server error) error. This usually means that there is a problem with the API, and it can be very difficult to find a fix for this.

Also, make sure that your application has full access to your endpoint.There are a few things you can check to make sure that you have all of the requirements and dependencies in place, but most of these errors can happen because you have not set up your API properly, so that is a good place to start.

Are there any issues with your application?

Sometimes, you can get an issue in your code or your application even if the environment is working properly. This is more difficult to track down and can be more specific than the API issue.

I can try running the tests in a clean test environment again. This way we can isolate if there is an issue with the code or with the tests.

If you're just getting started with Bot Builder and creating bots, I suggest creating a separate branch in BitBucket or GitHub that you can quickly test in, and if the tests pass then merge it back into master. This will help you to be able to more easily determine if an issue is actually with your code or the environment.

How do I change the name of my endpoint?

Endpoints are not the same as channels. For example, your default endpoint is botframework.ai. However, you may want to have different channels that communicate with different bots. To name the channel you can just put the name after your endpoint, like this: botframework.ai/bookit. This will tell the bot to talk to the botframework.ai/bookit endpoint.

If you want the bots to talk to each other, you'll have to make sure that they are communicating with the right endpoint.

Are you sure this endpoint is working?

The first step in debugging a working bot is to make sure that the bot and the API are working.

You can do this by testing the bot's responses with Postman, and checking that the bot does not receive a botframework.



Comments:

  1. Mezikora

    This is just a peerless topic.

  2. Lonell

    And with this I have come across. We can communicate on this topic.

  3. JoJobei

    Not at all.

  4. Mazulkis

    I have an idea, if you're interested, you can talk about it ...



Write a message